diff options
author | 2018-07-18 15:39:37 -0700 | |
---|---|---|
committer | 2018-08-29 09:20:48 -0700 | |
commit | 119248bec9d318ae41da8ab8f400f07e7a610cc3 (patch) | |
tree | a573e308403ac5f16cb38bd49061d09e661580f6 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | rcutorture: Add forward-progress tests for RCU grace periods (diff) | |
download | wireguard-linux-119248bec9d318ae41da8ab8f400f07e7a610cc3.tar.xz wireguard-linux-119248bec9d318ae41da8ab8f400f07e7a610cc3.zip |
rcutorture: Also use GP sequence to judge forward progress
Currently, rcutorture relies solely on the progress of
rcu_torture_writer() to judge grace-period forward progress. In theory,
this is the gold standard of forward progress, but in practice rcutorture
separately detects and reports rcu_torture_writer() stalls. This commit
therefore adds the grace-period sequence number (when provided) to the
judgment of grace-period forward progress, which makes it easier to
distinguish between failure of actual grace periods to progress on the
one hand and downstream forward-progress failures on the other.
For example, given this change, if rcu_torture_writer() stalls,
but rcu_torture_fwd_prog() does not complain, then the grace-period
computation is working, which is a hint that the failure lies in callback
processing, wakeup of the rcu_torture_writer() kthread, or similar.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions