Lines Matching refs:that

14 spinlock itself will guarantee the global lock, so it will guarantee that
15 there is only one thread-of-control within the region(s) protected by that
28 sequences that you _know_ need to be split up: avoid it at all cost if you
35 easily added to places that are completely independent of other code (for
36 example, internal driver data structures that nobody else ever touches).
39    to do locking across CPU's, which implies that EVERYTHING that
64 	.. critical section that only reads the info ...
73 itself.  The read lock allows many concurrent readers.  Anything that
92 are the most safe ones, and the ones that work under all circumstances,
100 cheaper versions of the spinlocks. IFF you know that the spinlocks are
109 This is useful if you know that the data in question is only ever
112 The reasons you mustn't use these versions if you have interrupts that
113 play with the spinlock is that you can get deadlocks:
122 interrupt happens on the same CPU that already holds the lock, because the
130 CPU that holds the lock, so the lock-holder can continue and eventually
133 Note that you can be clever with read-write locks and interrupts. For
134 example, if you know that the interrupt only ever gets a read-lock, then