Lines Matching full:classes

19 The validator tracks the 'usage state' of lock-classes, and it tracks
20 the dependencies between different lock-classes. Lock usage indicates
154 between any two lock-classes::
321 is O(N^2), so even with just a few hundred lock-classes we'd have to do
336 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
342 desktop systems have less than 1,000 lock classes, so this warning
348 	load of the module will create a new set of lock classes for
350 	classes (see below discussion of reuse of lock classes for why).
352 	the number of lock classes will eventually reach the maximum.
357 	spinlock_t will consume 8192 lock classes -unless- each spinlock
369 lock classes to be reused.  However, if you are tempted to make this
371 be required, keeping in mind that the lock classes to be removed are
375 Of course, if you do run out of lock classes, the next thing to do is
376 to find the offending lock classes.  First, the following command gives
377 you the number of lock classes currently in use along with the maximum::
379 	grep "lock-classes" /proc/lockdep_stats
383 	lock-classes:                          748 [max: 8191]
387 identify the leaking lock classes::