Lines Matching refs:acquire

124 - acquire operations will appear to happen, with respect to the other
132 - release operations will *synchronize with* acquire operations;
298 either *acquire* or *release* semantics [#rmw]_.  This has two effects:
300 .. [#rmw] Read-modify-write operations can have both---acquire applies to the
304   (for acquire) or after previous operations (for release).
306 - if a release operation in one thread *synchronizes with* an acquire operation
310   acquire operation in the second thread.
312 The concept of acquire and release semantics is not exclusive to atomic
314 acquire or release semantics.  For example:
316 - ``pthread_mutex_lock`` has acquire semantics, ``pthread_mutex_unlock`` has
322   ``pthread_mutex_lock``) and acquire semantics (synchronizing with
326   of the new thread; ``pthread_join`` has acquire semantics and synchronizes
330   acquire semantics.
334 (release) and ``pthread_join`` (acquire):
347 a release operation and an acquire operation.  Therefore, atomic operations
349 paired with another operation of the opposite kind: an acquire operation
356 as acquire operations.  ``smp_wmb()``, ``smp_mb_release()``,
358 operations.  ``smp_mb()`` counts as both acquire and release, therefore
375 with* a load-acquire on a variable ``x``, while a release barrier
376 synchronizes with any acquire operation.  The following example shows
396 the acquire operation, and vice versa.  In fact, this happened already
464   operation consist of just a load-acquire followed by a store-release.