Lines Matching refs:barrier

38 proper implicit or explicit read memory barrier is needed before reading the
59 or explicit memory barrier is needed before the value set with the operation
69 implicit or explicit memory barrier is used after possible runtime
74 barrier.
84 barrier for each use case.  Failure to do so will result in code that may
118 Alternatively, you could place a barrier() call in the loop.
214 memory barrier semantics which satisfy the above requirements, that is
224 This means that like atomic_{inc,dec}_return(), the memory barrier
236 Again, these primitives provide explicit memory barrier semantics around
243 provide explicit memory barrier semantics around the operation.
249 This primitive must provide explicit memory barrier semantics around
290 If a caller requires memory barrier semantics around an atomic_t
313 A missing memory barrier in the cases where they are required by the
378  the atomic_t memory barrier requirements quite clearly.)
404 With the memory barrier semantics required of the atomic_t operations
424 their SMP and memory barrier semantics are similar in shape and scope
439 They must execute atomically, yet there are no implicit memory barrier
465 must provide explicit memory barrier semantics around their execution.
490 not return a value, and thus does not need to provide memory barrier
510 There are two special bitops with lock barrier semantics (acquire/release,
521 unlock barrier semantics. This can be useful if the lock itself is protecting
539 barrier semantics.
542 memory-barrier semantics as the atomic and bit operations returning
549 Spinlocks and rwlocks have memory barrier expectations as well.
570 It is actually pretty simple to get the memory barrier correct.