Lines Matching refs:class

7 Lock-class
10 The basic object the validator operates upon is a 'class' of locks.
12 A class of locks is a group of locks that are logically the same with
15 struct is one class, while each inode has its own instantiation of that
16 lock class.
22 Unlike an lock instantiation, the lock-class itself never goes away: when
23 a lock-class is used for the first time after bootup it gets registered,
24 and all subsequent uses of that lock-class will be attached to this
25 lock-class.
30 The validator tracks lock-class usage history into 4n + 1 separate state bits:
68 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
70 set for any lock-class:
81 The same lock-class must not be acquired twice, because this could lead
110 When a lock-class changes its state, the following aspects of the above
134 instance of the same lock-class. Such cases typically happen when there
166 separate (sub)class for the purposes of validation.
179 combination and timing of these locking sequences can cause any class of
235 normally results from lock-class leakage or failure to properly
239 	will result in lock-class leakage.  The issue here is that each
253 	the per-bucket spinlocks would guarantee lock-class overflow.
255 	would place all 8192 locks into a single lock class.