Lines Matching refs:memory

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
73 interface must take care of that with a proper implicit or explicit memory
83 or processor, and explicitly invoke the appropriate compiler and/or memory
150 and never changed later, so that memory barriers are not needed:
173 Don't even -think- about doing this without proper use of memory barriers,
192 require any explicit memory barriers.  They need only perform the
205 include explicit memory barriers that are performed before and after
206 the operation.  It must be done such that all memory operations before
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
260 atomic_xchg must provide explicit memory barriers around the operation.
269 atomic_cmpxchg must provide explicit memory barriers around the operation,
270 although if the comparison fails then no memory ordering guarantees are
284 atomic_add_unless must provide explicit memory barriers around the
290 If a caller requires memory barrier semantics around an atomic_t
303 It makes sure that all memory operations preceding the atomic_dec()
313 A missing memory barrier in the cases where they are required by the
377  found a bug wrt. memory barriers in kfree_skb() that exposed
378  the atomic_t memory barrier requirements quite clearly.)
404 With the memory barrier semantics required of the atomic_t operations
405 which return values, the above sequence of memory visibility can never
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.
466 All memory operations before the atomic bit operation call must be
469 subsequent memory operation is made visible.  For example:
477 "obj->dead = 1;" is visible to cpus before the atomic memory operation
479 memory operation done by test_and_set_bit() must become visible before
489 If explicit memory barriers are required around {set,clear}_bit() (which do
490 not return a value, and thus does not need to provide memory barrier
499 	/* All memory operations before this call will
506 	 * subsequent memory operations.
538 These non-atomic variants also do not require any special memory
542 memory-barrier semantics as the atomic and bit operations returning
549 Spinlocks and rwlocks have memory barrier expectations as well.
553    visible before any subsequent memory operation.
556    all previous memory operations are globally visible before the
570 It is actually pretty simple to get the memory barrier correct.
573 subsequent memory operation.
630 Now, as far as memory barriers go, as long as spin_lock()
631 strictly orders all subsequent memory operations (including
639 is not dropping to zero, there are no memory ordering