Lines Matching refs:mutexes

4 Please read mutex-design.txt first, as it applies to wait/wound mutexes too.
43 Compared to normal mutexes two additional concepts/objects show up in the lock
44 interface for w/w mutexes:
52 W/w class: In contrast to normal mutexes the lock class needs to be explicit for
53 w/w mutexes, since it is required to initialize the acquire context.
212 mutexes are a natural fit for such a case for two reasons:
310   increase in code size if wait/wound mutexes are not used.
315   would add overhead to all cases where normal mutexes are used, and
325    - Attempting to lock more mutexes after ww_acquire_done.
327      unlocking all mutexes.
329      before unlocking all mutexes.
333    - Unlocking mutexes with the wrong unlock function.