Lines Matching full:barrier

44 proper implicit or explicit read memory barrier is needed before reading the
65 or explicit memory barrier is needed before the value set with the operation
75 implicit or explicit memory barrier is used after possible runtime
80 barrier.
92 	appropriate compiler and/or memory barrier for each use case.  Failure
124 Alternatively, you could place a barrier() call in the loop.
184 	``READ_ONCE()`` OR ``WRITE_ONCE()`` DO NOT IMPLY A BARRIER!
222 memory barrier semantics which satisfy the above requirements, that is
232 This means that like atomic_{inc,dec}_return(), the memory barrier
244 Again, these primitives provide explicit memory barrier semantics around
251 provide explicit memory barrier semantics around the operation::
257 This primitive must provide explicit memory barrier semantics around
298 If a caller requires memory barrier semantics around an atomic_t
326 A missing memory barrier in the cases where they are required by the
392 	memory barriers in kfree_skb() that exposed the atomic_t memory barrier
419 With the memory barrier semantics required of the atomic_t operations
443 their SMP and memory barrier semantics are similar in shape and scope
458 They must execute atomically, yet there are no implicit memory barrier
486 must provide explicit memory barrier semantics around their execution.
511 not return a value, and thus does not need to provide memory barrier
531 There are two special bitops with lock barrier semantics (acquire/release,
542 unlock barrier semantics. This can be useful if the lock itself is protecting
560 barrier semantics.
563 memory-barrier semantics as the atomic and bit operations returning
572 Spinlocks and rwlocks have memory barrier expectations as well.
593 It is actually pretty simple to get the memory barrier correct.