Lines Matching refs:of
21 restart the tests, regardless of the initial state specified by the
33 fqs_duration Duration (in microseconds) of artificially induced bursts
34 of force_quiescent_state() invocations. In RCU
43 of calls to force_quiescent_state().
56 done via timers. Defaults to "1" for variants of RCU that
57 permit this. (Or, more accurately, variants of RCU that do
61 in which case n_barrier_cbs specifies the number of
65 synchronous RCU implementation (one for which a member of
70 nfakewriters This is the number of RCU fake writer threads to run. Fake
72 current readers" function of the interface selected by
74 different numbers of writers running in parallel.
79 nreaders This is the number of RCU reading threads supported.
80 The default is twice the number of CPUs. Why twice?
85 The number of seconds between each attempt to execute a
89 CPU-hotplug operations regardless of what value is
92 onoff_holdoff The number of seconds to wait until starting CPU-hotplug
100 The number of seconds to keep the test threads affinitied
101 to a particular subset of the CPUs, defaults to 3 seconds.
104 shutdown_secs The number of seconds to run the test before terminating
109 stall_cpu The number of seconds that a CPU should be stalled while
120 warnings in other parts of the kernel. You have been
124 The number of seconds to wait after rcutorture starts
127 stat_interval The number of seconds between output of torture
128 statistics (via printk()). Regardless of the interval,
134 stutter The length of time to run the test before pausing for this
135 same period of time. Defaults to "stutter=5", so as
140 test_boost Whether or not to test the ability of RCU to do priority
152 The number of seconds in an RCU priority-inversion test
158 The number of seconds to do RCU priority-inversion testing
162 test_no_idle_hz Whether or not to test the ability of RCU to operate in
167 torture_type The type of RCU to test, with string values as follows:
178 of RCU in order to help test rcutorture itself.
200 …rcu-torture:--- Start of test: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_no_idle_…
205 …rcu-torture:--- End of test: SUCCESS: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_n…
209 use other commands to access the output of the printk()s used by
219 o "rtc": The hexadecimal address of the structure currently visible
222 o "ver": The number of times since boot that the RCU writer task
230 o "rta": Number of structures allocated from the torture freelist.
232 o "rtaf": Number of allocations from the torture freelist that have
234 to be non-zero, but it is bad for it to be a large fraction of
237 o "rtf": Number of frees into the torture freelist.
243 o "rtbe": A non-zero value indicates that one of the rcu_barrier()
244 family of functions is not working correctly.
251 to the real-time priority level of 1. This value should be zero.
253 o "rtbf": The number of times that RCU priority boosting failed
256 o "rtb": The number of times that rcutorture attempted to force
261 o "nt": The number of times rcutorture ran RCU read-side code from
265 o "Reader Pipe": Histogram of "ages" of structures seen by readers.
268 you notice. The age of a newly allocated structure is zero,
277 o "Reader Batch": Another histogram of "ages" of structures seen
278 by readers, but in terms of counter flips (or batches) rather
279 than in terms of grace periods. The legal number of non-zero
284 o "Free-Block Circulation": Shows the number of torture structures
286 should closely correspond to the number of structures allocated,
288 and all but the last remaining to the corresponding number of
293 Different implementations of RCU can provide implementation-specific
300 the values of the "old" and "current" counters for the corresponding CPU.
316 The output can be manually inspected for the error flag of "!!!".
317 One could of course create a more elaborate script that automatically