Difference between revisions of "cpp/thread/condition variable"
(let's just roll back that recently-added big second example, it doesn't even add much) |
(c -> c/core.) |
||
(27 intermediate revisions by 17 users not shown) | |||
Line 1: | Line 1: | ||
{{cpp/title|condition_variable}} | {{cpp/title|condition_variable}} | ||
{{cpp/thread/condition_variable/navbar}} | {{cpp/thread/condition_variable/navbar}} | ||
− | {{ddcl | header=condition_variable | since=c++11 | 1= | + | {{ddcl|header=condition_variable|since=c++11|1= |
class condition_variable; | class condition_variable; | ||
}} | }} | ||
− | + | {{tt|std::condition_variable}} is a synchronization primitive used with a {{lc|std::mutex}} to block one or more threads until another thread both modifies a shared variable (the ''condition'') and notifies the {{tt|std::condition_variable}}. | |
− | The thread that intends to modify the variable | + | The thread that intends to modify the shared variable must: |
− | # | + | # Acquire a {{lc|std::mutex}} (typically via {{lc|std::lock_guard}}). |
− | # | + | # Modify the shared variable while the lock is owned. |
− | # | + | # Call {{lc|notify_one}} or {{lc|notify_all}} on the {{tt|std::condition_variable}} (can be done after releasing the lock). |
− | Even if the shared variable is atomic, it must be modified | + | Even if the shared variable is atomic, it must be modified while owning the mutex to [https://stackoverflow.com/questions/38147825/ correctly] publish the modification to the waiting thread. |
− | Any thread that intends to wait on {{tt|std::condition_variable}} | + | Any thread that intends to wait on a {{tt|std::condition_variable}} must: |
− | # | + | # Acquire a {{c/core|std::unique_lock<std::mutex>}} on the mutex used to protect the shared variable. |
− | # | + | # Do one of the following: |
− | + | :# Check the condition, in case it was already updated and notified. | |
+ | :# Call {{lc|wait}}, {{lc|wait_for}}, or {{lc|wait_until}} on the {{tt|std::condition_variable}} (atomically releases the mutex and suspends thread execution until the condition variable is notified, a timeout expires, or a {{enwiki|Spurious wakeup|spurious wakeup}} occurs, then atomically acquires the mutex before returning). | ||
+ | :# Check the condition and resume waiting if not satisfied. | ||
+ | :: or: | ||
+ | :# Use the predicated overload of {{lc|wait}}, {{lc|wait_for}}, and {{lc|wait_until}}, which performs the same three steps. | ||
− | {{tt|std::condition_variable}} works only with {{c|std::unique_lock<std::mutex>}} | + | {{tt|std::condition_variable}} works only with {{c/core|std::unique_lock<std::mutex>}}, which allows for maximal efficiency on some platforms. {{lc|std::condition_variable_any}} provides a condition variable that works with any {{named req|BasicLockable}} object, such as {{lc|std::shared_lock}}. |
Condition variables permit concurrent invocation of the {{lc|wait}}, {{lc|wait_for}}, {{lc|wait_until}}, {{lc|notify_one}} and {{lc|notify_all}} member functions. | Condition variables permit concurrent invocation of the {{lc|wait}}, {{lc|wait_for}}, {{lc|wait_until}}, {{lc|notify_one}} and {{lc|notify_all}} member functions. | ||
Line 24: | Line 28: | ||
The class {{tt|std::condition_variable}} is a {{named req|StandardLayoutType}}. It is not {{named req|CopyConstructible}}, {{named req|MoveConstructible}}, {{named req|CopyAssignable}}, or {{named req|MoveAssignable}}. | The class {{tt|std::condition_variable}} is a {{named req|StandardLayoutType}}. It is not {{named req|CopyConstructible}}, {{named req|MoveConstructible}}, {{named req|CopyAssignable}}, or {{named req|MoveAssignable}}. | ||
− | === | + | ===Nested types=== |
{{dsc begin}} | {{dsc begin}} | ||
− | {{dsc hitem | | + | {{dsc hitem|Name|Definition}} |
− | {{dsc | {{tt|native_handle_type}} | | + | {{dsc|{{tt|native_handle_type}}|implementation-defined}} |
{{dsc end}} | {{dsc end}} | ||
===Member functions=== | ===Member functions=== | ||
{{dsc begin}} | {{dsc begin}} | ||
− | {{dsc inc | cpp/thread/condition_variable/dsc constructor | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc constructor|condition_variable}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc destructor | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc destructor|condition_variable}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc operator{{=}} | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc operator{{=}}|condition_variable}} |
− | {{dsc h2 | Notification}} | + | {{dsc h2|Notification}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc notify_one | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc notify_one|condition_variable}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc notify_all | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc notify_all|condition_variable}} |
− | {{dsc h2 | Waiting}} | + | {{dsc h2|Waiting}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc wait | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc wait|condition_variable}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc wait_for | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc wait_for|condition_variable}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc wait_until | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc wait_until|condition_variable}} |
− | {{dsc h2 | Native handle}} | + | {{dsc h2|Native handle}} |
− | {{dsc inc | cpp/thread/condition_variable/dsc native handle | condition_variable}} | + | {{dsc inc|cpp/thread/condition_variable/dsc native handle|condition_variable}} |
{{dsc end}} | {{dsc end}} | ||
===Example=== | ===Example=== | ||
− | {{example| {{tt|condition_variable}} is used in combination with a {{lc|std::mutex}} to facilitate inter-thread communication. | + | {{example |
+ | |{{tt|std::condition_variable}} is used in combination with a {{lc|std::mutex}} to facilitate inter-thread communication. | ||
|code= | |code= | ||
+ | #include <condition_variable> | ||
#include <iostream> | #include <iostream> | ||
+ | #include <mutex> | ||
#include <string> | #include <string> | ||
#include <thread> | #include <thread> | ||
− | |||
− | |||
std::mutex m; | std::mutex m; | ||
Line 66: | Line 71: | ||
void worker_thread() | void worker_thread() | ||
{ | { | ||
− | // | + | // wait until main() sends data |
− | std::unique_lock | + | std::unique_lock lk(m); |
− | cv.wait(lk, []{return ready;}); | + | cv.wait(lk, []{ return ready; }); |
− | + | ||
− | // after the wait, we own the lock | + | // after the wait, we own the lock |
std::cout << "Worker thread is processing data\n"; | std::cout << "Worker thread is processing data\n"; | ||
data += " after processing"; | data += " after processing"; | ||
− | + | ||
− | // | + | // send data back to main() |
processed = true; | processed = true; | ||
std::cout << "Worker thread signals data processing completed\n"; | std::cout << "Worker thread signals data processing completed\n"; | ||
− | // | + | // manual unlocking is done before notifying, to avoid waking up |
// the waiting thread only to block again (see notify_one for details) | // the waiting thread only to block again (see notify_one for details) | ||
lk.unlock(); | lk.unlock(); | ||
Line 87: | Line 92: | ||
{ | { | ||
std::thread worker(worker_thread); | std::thread worker(worker_thread); | ||
− | + | ||
data = "Example data"; | data = "Example data"; | ||
// send data to the worker thread | // send data to the worker thread | ||
{ | { | ||
− | std::lock_guard | + | std::lock_guard lk(m); |
ready = true; | ready = true; | ||
std::cout << "main() signals data ready for processing\n"; | std::cout << "main() signals data ready for processing\n"; | ||
} | } | ||
cv.notify_one(); | cv.notify_one(); | ||
− | + | ||
// wait for the worker | // wait for the worker | ||
{ | { | ||
− | std::unique_lock | + | std::unique_lock lk(m); |
− | cv.wait(lk, []{return processed;}); | + | cv.wait(lk, []{ return processed; }); |
} | } | ||
std::cout << "Back in main(), data = " << data << '\n'; | std::cout << "Back in main(), data = " << data << '\n'; | ||
− | + | ||
worker.join(); | worker.join(); | ||
} | } | ||
− | | output= | + | |output= |
main() signals data ready for processing | main() signals data ready for processing | ||
Worker thread is processing data | Worker thread is processing data | ||
Line 113: | Line 118: | ||
}} | }} | ||
− | + | ===See also=== | |
− | + | {{dsc begin}} | |
− | + | {{dsc inc|cpp/thread/dsc condition_variable_any}} | |
− | + | {{dsc inc|cpp/thread/dsc mutex}} | |
− | + | {{dsc inc|cpp/thread/dsc lock_guard}} | |
− | + | {{dsc inc|cpp/thread/dsc unique_lock}} | |
− | + | {{dsc end}} | |
− | + | ||
+ | {{langlinks|de|es|fr|it|ja|pt|ru|zh}} |
Latest revision as of 22:17, 4 March 2024
Defined in header <condition_variable>
|
||
class condition_variable; |
(since C++11) | |
std::condition_variable
is a synchronization primitive used with a std::mutex to block one or more threads until another thread both modifies a shared variable (the condition) and notifies the std::condition_variable
.
The thread that intends to modify the shared variable must:
- Acquire a std::mutex (typically via std::lock_guard).
- Modify the shared variable while the lock is owned.
- Call notify_one or notify_all on the
std::condition_variable
(can be done after releasing the lock).
Even if the shared variable is atomic, it must be modified while owning the mutex to correctly publish the modification to the waiting thread.
Any thread that intends to wait on a std::condition_variable
must:
- Acquire a std::unique_lock<std::mutex> on the mutex used to protect the shared variable.
- Do one of the following:
- Check the condition, in case it was already updated and notified.
- Call wait, wait_for, or wait_until on the
std::condition_variable
(atomically releases the mutex and suspends thread execution until the condition variable is notified, a timeout expires, or a spurious wakeup occurs, then atomically acquires the mutex before returning). - Check the condition and resume waiting if not satisfied.
- or:
- Use the predicated overload of wait, wait_for, and wait_until, which performs the same three steps.
std::condition_variable
works only with std::unique_lock<std::mutex>, which allows for maximal efficiency on some platforms. std::condition_variable_any provides a condition variable that works with any BasicLockable object, such as std::shared_lock.
Condition variables permit concurrent invocation of the wait, wait_for, wait_until, notify_one and notify_all member functions.
The class std::condition_variable
is a StandardLayoutType. It is not CopyConstructible, MoveConstructible, CopyAssignable, or MoveAssignable.
Contents |
[edit] Nested types
Name | Definition |
native_handle_type
|
implementation-defined |
[edit] Member functions
constructs the object (public member function) | |
destructs the object (public member function) | |
operator= [deleted] |
not copy-assignable (public member function) |
Notification | |
notifies one waiting thread (public member function) | |
notifies all waiting threads (public member function) | |
Waiting | |
blocks the current thread until the condition variable is awakened (public member function) | |
blocks the current thread until the condition variable is awakened or after the specified timeout duration (public member function) | |
blocks the current thread until the condition variable is awakened or until specified time point has been reached (public member function) | |
Native handle | |
returns the native handle (public member function) |
[edit] Example
std::condition_variable
is used in combination with a std::mutex to facilitate inter-thread communication.
#include <condition_variable> #include <iostream> #include <mutex> #include <string> #include <thread> std::mutex m; std::condition_variable cv; std::string data; bool ready = false; bool processed = false; void worker_thread() { // wait until main() sends data std::unique_lock lk(m); cv.wait(lk, []{ return ready; }); // after the wait, we own the lock std::cout << "Worker thread is processing data\n"; data += " after processing"; // send data back to main() processed = true; std::cout << "Worker thread signals data processing completed\n"; // manual unlocking is done before notifying, to avoid waking up // the waiting thread only to block again (see notify_one for details) lk.unlock(); cv.notify_one(); } int main() { std::thread worker(worker_thread); data = "Example data"; // send data to the worker thread { std::lock_guard lk(m); ready = true; std::cout << "main() signals data ready for processing\n"; } cv.notify_one(); // wait for the worker { std::unique_lock lk(m); cv.wait(lk, []{ return processed; }); } std::cout << "Back in main(), data = " << data << '\n'; worker.join(); }
Output:
main() signals data ready for processing Worker thread is processing data Worker thread signals data processing completed Back in main(), data = Example data after processing
[edit] See also
(C++11) |
provides a condition variable associated with any lock type (class) |
(C++11) |
provides basic mutual exclusion facility (class) |
(C++11) |
implements a strictly scope-based mutex ownership wrapper (class template) |
(C++11) |
implements movable mutex ownership wrapper (class template) |