32 Concurrency support library [thread]

32.5 Atomic operations [atomics]

32.5.6 Waiting and notifying [atomics.wait]

Atomic waiting operations and atomic notifying operations provide a mechanism to wait for the value of an atomic object to change more efficiently than can be achieved with polling.

An atomic waiting operation may block until it is unblocked by an atomic notifying operation, according to each function's effects.

[Note 1:

Programs are not guaranteed to observe transient atomic values, an issue known as the A-B-A problem, resulting in continued blocking if a condition is only temporarily met.

— end note]

[Note 2:

The following functions are atomic waiting operations:

(2.1)
atomic<T>::wait,
(2.2)
atomic_flag::wait,
(2.3)
atomic_wait and atomic_wait_explicit,
(2.4)
atomic_flag_wait and atomic_flag_wait_explicit, and
(2.5)
atomic_ref<T>::wait.

— end note]

[Note 3:

The following functions are atomic notifying operations:

(3.1)
atomic<T>::notify_one and atomic<T>::notify_all,
(3.2)
atomic_flag::notify_one and atomic_flag::notify_all,
(3.3)
atomic_notify_one and atomic_notify_all,
(3.4)
atomic_flag_notify_one and atomic_flag_notify_all, and
(3.5)
atomic_ref<T>::notify_one and atomic_ref<T>::notify_all.

— end note]

A call to an atomic waiting operation on an atomic object M is eligible to be unblocked by a call to an atomic notifying operation on M if there exist side effects X and Y on M such that:

(4.1)
the atomic waiting operation has blocked after observing the result of X,
(4.2)
X precedes Y in the modification order of M, and
(4.3)
Y happens before the call to the atomic notifying operation.