Lines Matching refs:RELEASE
477 An ACQUIRE operation should almost always be paired with a RELEASE
481 (6) RELEASE operations.
484 memory operations before the RELEASE operation will appear to happen
485 before the RELEASE operation with respect to the other components of the
486 system. RELEASE operations include UNLOCK operations and
489 Memory operations that occur after a RELEASE operation may appear to
492 The use of ACQUIRE and RELEASE operations generally precludes the need
493 for other sorts of memory barrier. In addition, a RELEASE+ACQUIRE pair is
496 RELEASE on that same variable are guaranteed to be visible. In other
502 RELEASE acts as a minimal "release" operation.
505 RELEASE variants in addition to fully-ordered and relaxed (no barrier
507 store, ACQUIRE semantics apply only to the load and RELEASE semantics apply
1976 In all cases there are variants on "ACQUIRE" operations and "RELEASE" operations
1987 (2) RELEASE operation implication:
1989 Memory operations issued before the RELEASE will be completed before the
1990 RELEASE operation has completed.
1992 Memory operations issued after the RELEASE may be completed before the
1993 RELEASE operation has completed.
2000 (4) ACQUIRE vs RELEASE implication:
2002 All ACQUIRE operations issued before a RELEASE operation will be
2003 completed before the RELEASE operation.
2016 An ACQUIRE followed by a RELEASE may not be assumed to be full memory barrier
2018 ACQUIRE, and an access following the RELEASE to happen before the RELEASE, and
2023 RELEASE M
2028 ACQUIRE M, STORE *B, STORE *A, RELEASE M
2030 When the ACQUIRE and RELEASE are a lock acquisition and release,
2032 RELEASE are to the same lock variable, but only from the perspective of
2034 RELEASE may -not- be assumed to be a full memory barrier.
2036 Similarly, the reverse case of a RELEASE followed by an ACQUIRE does
2038 critical sections corresponding to the RELEASE and the ACQUIRE can cross,
2042 RELEASE M
2048 ACQUIRE N, STORE *B, STORE *A, RELEASE M
2052 the RELEASE would simply complete, thereby avoiding the deadlock.
2092 RELEASE
2098 ACQUIRE, {*F,*A}, *E, {*C,*D}, *B, RELEASE
2104 {*F,*A}, *B, ACQUIRE, *C, *D, RELEASE, *E
2105 *A, *B, *C, ACQUIRE, *D, RELEASE, *E, *F
2106 *A, *B, ACQUIRE, *C, RELEASE, *D, *E, *F
2107 *B, ACQUIRE, *C, *D, RELEASE, {*F,*A}, *E
2115 (RELEASE equivalent) will act as compiler barriers only. So if memory or I/O
2301 RELEASE M RELEASE Q
2308 *E, ACQUIRE M, ACQUIRE Q, *G, *C, *F, *A, *B, RELEASE Q, *D, *H, RELEASE M
2313 *A, *B or *C following RELEASE M
2315 *E, *F or *G following RELEASE Q
2381 RELEASE task
2423 RELEASE task