Lines Matching refs:of

14 This torture test consists of creating a number of kernel threads which
15 acquire the lock and hold it for specific amount of time, thus simulating
16 different critical region behaviors. The amount of contention on the lock
28 nwriters_stress   Number of kernel threads that will stress exclusive lock
30 		  of online CPUs.
32 nreaders_stress   Number of kernel threads that will stress shared lock
33 		  ownership (readers). The default is the same amount of writer
35 		  both readers and writers be the amount of online CPUs.
37 torture_type	  Type of lock to torture. By default, only spinlocks will
68 shutdown_secs	  The number of seconds to run the test before terminating
73 onoff_interval	  The number of seconds between each attempt to execute a
77 		  refuse to do any CPU-hotplug operations regardless of
80 onoff_holdoff	  The number of seconds to wait until starting CPU-hotplug
88 stat_interval	  Number of seconds between statistics-related printk()s.
94 stutter		  The length of time to run the test before pausing for this
95 		  same period of time.  Defaults to "stutter=5", so as
100 shuffle_interval  The number of seconds to keep the test threads affinitied
101 		  to a particular subset of the CPUs, defaults to 3 seconds.
119 (B): Number of writer lock acquisitions. If dealing with a read/write primitive
122 (C): Number of times the lock was acquired.
124 (D): Min and max number of times threads failed to acquire the lock.
129      Of course, the same applies for (C), above. A dummy example of this is
143 The output can be manually inspected for the error flag of "!!!".
144 One could of course create a more elaborate script that automatically