Lines Matching refs:torture

8 be loaded to run a torture test.  The test periodically outputs
10 command (perhaps grepping for "torture").  The test is started
18 whether the RCU torture tests are to be started immediately during
24 You will normally -not- want to start the RCU torture tests during boot
127 stat_interval	The number of seconds between output of torture
200 …rcu-torture:--- Start of test: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_no_idle_…
201 …rcu-torture: rtc:           (null) ver: 155441 tfle: 0 rta: 155441 rtaf: 8884 rtf: 155440 rtmbe: 0…
202 	rcu-torture: Reader Pipe:  727860534 34213 0 0 0 0 0 0 0 0 0
203 	rcu-torture: Reader Batch:  727877838 17003 0 0 0 0 0 0 0 0 0
204 …rcu-torture: Free-Block Circulation:  155440 155440 155440 155440 155440 155440 155440 155440 1554…
205 …rcu-torture:--- End of test: SUCCESS: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_n…
207 The command "dmesg | grep torture:" will extract this information on
210 the RCU torture test.  The printk()s use KERN_ALERT, so they should
225 o	"tfle": If non-zero, indicates that the "torture freelist"
230 o	"rta": Number of structures allocated from the torture freelist.
232 o	"rtaf": Number of allocations from the torture freelist that have
237 o	"rtf": Number of frees into the torture freelist.
284 o	"Free-Block Circulation": Shows the number of torture structures
290 	as it is only incremented if a torture structure's counter
297 	srcu-torture: per-CPU(idx=1): 0(0,1) 1(0,1) 2(0,0) 3(0,1)
307 The following script may be used to torture RCU:
314 	dmesg | grep torture: