Lines Matching refs:operations

25 The first operations to implement for atomic_t's are the initializers and
35 The initializer is atomic in that the return values of the atomic operations
56 The setting is atomic in that the return values of the atomic operations by
68 values initialized or modified with the interface operations if a proper
71 interface operations.  atomic_read does not guarantee that the runtime
174 locks, or atomic operations if variable a can change at runtime!
206 the operation.  It must be done such that all memory operations before
265 with the given old and new values. Like all atomic_xxx operations,
267 other accesses of *v are performed through atomic_xxx operations.
303 It makes sure that all memory operations preceding the atomic_dec()
404 With the memory barrier semantics required of the atomic_t operations
420 Another note is that the atomic_t operations returning values are
423 We will now cover the atomic bitmask operations.  You will find that
427 Native atomic bit operations are defined to operate on objects aligned
460 flag operations.  Routines such as test_and_set_ti_thread_flag() chop
464 These routines, like the atomic_t counter operations returning values,
466 All memory operations before the atomic bit operation call must be
499 	/* All memory operations before this call will
506 	 * subsequent memory operations.
514 bit_spin_unlock type operations without specifying any more barriers.
524 Finally, there are non-atomic versions of the bitmask operations
527 expensive non-atomic operations may be used in the implementation.
542 memory-barrier semantics as the atomic and bit operations returning
556    all previous memory operations are globally visible before the
631 strictly orders all subsequent memory operations (including