Lines Matching refs:classes

18 The validator tracks the 'state' of lock-classes, and it tracks
19 dependencies between different lock-classes. The validator maintains a
95 between any two lock-classes:
260 is O(N^2), so even with just a few hundred lock-classes we'd have to do
275 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
281 desktop systems have less than 1,000 lock classes, so this warning
287 	load of the module will create a new set of lock classes for
289 	classes (see below discussion of reuse of lock classes for why).
291 	the number of lock classes will eventually reach the maximum.
296 	spinlock_t will consume 8192 lock classes -unless- each spinlock
308 lock classes to be reused.  However, if you are tempted to make this
310 be required, keeping in mind that the lock classes to be removed are
314 Of course, if you do run out of lock classes, the next thing to do is
315 to find the offending lock classes.  First, the following command gives
316 you the number of lock classes currently in use along with the maximum:
318 	grep "lock-classes" /proc/lockdep_stats
322 	 lock-classes:                          748 [max: 8191]
326 identify the leaking lock classes: