Lines Matching refs:RELEASE
481 An ACQUIRE operation should almost always be paired with a RELEASE
485 (6) RELEASE operations.
488 memory operations before the RELEASE operation will appear to happen
489 before the RELEASE operation with respect to the other components of the
490 system. RELEASE operations include UNLOCK operations and
493 Memory operations that occur after a RELEASE operation may appear to
496 The use of ACQUIRE and RELEASE operations generally precludes the need
497 for other sorts of memory barrier. In addition, a RELEASE+ACQUIRE pair is
500 RELEASE on that same variable are guaranteed to be visible. In other
506 RELEASE acts as a minimal "release" operation.
509 RELEASE variants in addition to fully-ordered and relaxed (no barrier
511 store, ACQUIRE semantics apply only to the load and RELEASE semantics apply
1997 In all cases there are variants on "ACQUIRE" operations and "RELEASE" operations
2008 (2) RELEASE operation implication:
2010 Memory operations issued before the RELEASE will be completed before the
2011 RELEASE operation has completed.
2013 Memory operations issued after the RELEASE may be completed before the
2014 RELEASE operation has completed.
2021 (4) ACQUIRE vs RELEASE implication:
2023 All ACQUIRE operations issued before a RELEASE operation will be
2024 completed before the RELEASE operation.
2037 An ACQUIRE followed by a RELEASE may not be assumed to be full memory barrier
2039 ACQUIRE, and an access following the RELEASE to happen before the RELEASE, and
2044 RELEASE M
2049 ACQUIRE M, STORE *B, STORE *A, RELEASE M
2051 When the ACQUIRE and RELEASE are a lock acquisition and release,
2053 RELEASE are to the same lock variable, but only from the perspective of
2055 RELEASE may -not- be assumed to be a full memory barrier.
2057 Similarly, the reverse case of a RELEASE followed by an ACQUIRE does
2059 critical sections corresponding to the RELEASE and the ACQUIRE can cross,
2063 RELEASE M
2069 ACQUIRE N, STORE *B, STORE *A, RELEASE M
2073 the RELEASE would simply complete, thereby avoiding the deadlock.
2113 RELEASE
2119 ACQUIRE, {*F,*A}, *E, {*C,*D}, *B, RELEASE
2125 {*F,*A}, *B, ACQUIRE, *C, *D, RELEASE, *E
2126 *A, *B, *C, ACQUIRE, *D, RELEASE, *E, *F
2127 *A, *B, ACQUIRE, *C, RELEASE, *D, *E, *F
2128 *B, ACQUIRE, *C, *D, RELEASE, {*F,*A}, *E
2136 (RELEASE equivalent) will act as compiler barriers only. So if memory or I/O
2322 RELEASE M RELEASE Q
2329 *E, ACQUIRE M, ACQUIRE Q, *G, *C, *F, *A, *B, RELEASE Q, *D, *H, RELEASE M
2334 *A, *B or *C following RELEASE M
2336 *E, *F or *G following RELEASE Q
2402 RELEASE task
2444 RELEASE task