Lines Matching full:operations

2 Semantics and Behavior of Atomic and Bitmask Operations
11 Atomic Type And Operations
31 The first operations to implement for atomic_t's are the initializers and
41 The initializer is atomic in that the return values of the atomic operations
62 The setting is atomic in that the return values of the atomic operations by
74 values initialized or modified with the interface operations if a proper
77 interface operations.  atomic_read does not guarantee that the runtime
180 locks, or atomic operations if variable a can change at runtime!
214 the operation.  It must be done such that all memory operations before
273 with the given old and new values. Like all atomic_xxx operations,
275 other accesses of \*v are performed through atomic_xxx operations.
308 read-modify-write atomic operations.
316 It makes sure that all memory operations preceding the atomic_dec()
419 With the memory barrier semantics required of the atomic_t operations
435 Another note is that the atomic_t operations returning values are
442 We will now cover the atomic bitmask operations.  You will find that
446 Native atomic bit operations are defined to operate on objects aligned
481 flag operations.  Routines such as test_and_set_ti_thread_flag() chop
485 These routines, like the atomic_t counter operations returning values,
487 All memory operations before the atomic bit operation call must be
520 	/* All memory operations before this call will
527 	 * subsequent memory operations.
535 bit_spin_unlock type operations without specifying any more barriers. ::
545 Finally, there are non-atomic versions of the bitmask operations
548 expensive non-atomic operations may be used in the implementation.
563 memory-barrier semantics as the atomic and bit operations returning
579    all previous memory operations are globally visible before the
654 strictly orders all subsequent memory operations (including