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
157 between any two lock-classes::
324 is O(N^2), so even with just a few hundred lock-classes we'd have to do
339 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
345 desktop systems have less than 1,000 lock classes, so this warning
351 	load of the module will create a new set of lock classes for
353 	classes (see below discussion of reuse of lock classes for why).
355 	the number of lock classes will eventually reach the maximum.
360 	spinlock_t will consume 8192 lock classes -unless- each spinlock
372 lock classes to be reused.  However, if you are tempted to make this
374 be required, keeping in mind that the lock classes to be removed are
378 Of course, if you do run out of lock classes, the next thing to do is
379 to find the offending lock classes.  First, the following command gives
380 you the number of lock classes currently in use along with the maximum::
382 	grep "lock-classes" /proc/lockdep_stats
386 	lock-classes:                          748 [max: 8191]
390 identify the leaking lock classes::