Lines Matching full:operation

64 been set with this operation or set with another operation.  A proper implicit
65 or explicit memory barrier is needed before the value set with the operation
186 Now, we move onto the atomic operation interfaces typically implemented with
209 atomic_t and return the new counter value after the operation is
214 the operation.  It must be done such that all memory operations before
215 and after the atomic operation calls are strongly ordered with respect
216 to the atomic operation itself.
219 before and after the atomic operation.
245 the atomic operation::
251 provide explicit memory barrier semantics around the operation::
258 the operation.
264 This performs an atomic exchange operation on the atomic variable v, setting
266 just before the operation.
268 atomic_xchg must provide explicit memory barriers around the operation. ::
272 This performs an atomic compare exchange operation on the atomic value v,
277 atomic_cmpxchg must provide explicit memory barriers around the operation,
290 an atomic operation.
293 operation unless it fails (returns 0).
299 operation which does not return a value, a set of interfaces are
305 Preceding a non-value-returning read-modify-write atomic operation with
318 operation.  In the above example, it guarantees that the assignment of
432 on, and that lock protects the atomic operation.  Parisc uses the
467 operation.
487 All memory operations before the atomic bit operation call must be
488 made visible globally before the atomic bit operation is made visible.
489 Likewise, the atomic bit operation must be visible globally before any
490 subsequent memory operation is made visible.  For example::
498 "obj->dead = 1;" is visible to cpus before the atomic memory operation
500 memory operation done by test_and_set_bit() must become visible before
503 Finally there is the basic operation::
517 They are used as follows, and are akin to their atomic_t operation
549 They have names similar to the above bitmask operation interfaces,
576    visible before any subsequent memory operation.
595 sure the spinlock operation is globally visible before any
596 subsequent memory operation.
598 We can demonstrate this operation more clearly if we define
599 an abstract atomic operation::