Lines Matching refs:torture
13 be loaded to run a torture test. The test periodically outputs
15 command (perhaps grepping for "torture"). The test is started
26 …rcu-torture:--- Start of test: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_no_idle_…
27 …rcu-torture: rtc: (null) ver: 155441 tfle: 0 rta: 155441 rtaf: 8884 rtf: 155440 rtmbe: 0…
28 rcu-torture: Reader Pipe: 727860534 34213 0 0 0 0 0 0 0 0 0
29 rcu-torture: Reader Batch: 727877838 17003 0 0 0 0 0 0 0 0 0
30 …rcu-torture: Free-Block Circulation: 155440 155440 155440 155440 155440 155440 155440 155440 1554…
31 …rcu-torture:--- End of test: SUCCESS: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_n…
33 The command "dmesg | grep torture:" will extract this information on
36 the RCU torture test. The printk()s use KERN_ALERT, so they should
51 * "tfle": If non-zero, indicates that the "torture freelist"
56 * "rta": Number of structures allocated from the torture freelist.
58 * "rtaf": Number of allocations from the torture freelist that have
63 * "rtf": Number of frees into the torture freelist.
110 * "Free-Block Circulation": Shows the number of torture structures
116 as it is only incremented if a torture structure's counter
123 …srcud-torture: Tree SRCU per-CPU(idx=0): 0(35,-21) 1(-4,24) 2(1,1) 3(-26,20) 4(28,-47) 5(-9,4) 6(-…
135 It is sometimes desirable to torture RCU on a specific kernel build,
140 For example, the following script may be used to torture RCU::
147 dmesg | grep torture: