The solution to the producer-consumer problem is to use mutex locks and condition variables to achieve thread synchronization. 1. Use std::mutex and std::unique_lock to protect the shared buffer; 2. The producer waits through the condition variable when the buffer is full, and the consumer waits when the buffer is empty and the production has not ended; 3. After the producer generates data, the consumer notifies the producer after the consumer is notified; 4. After all producers complete, set the finished flag and notify the consumer to exit; 5. The consumer terminates the thread when the buffer is empty and the production is finished. This implementation ensures thread safety and correct synchronization, completely solving producer-consumer problems.
In multithreaded programming, the Producer-Consumer Problem is a classic synchronization problem. In C, it can be implemented through std::thread
, std::mutex
, std::condition_variable
and a shared buffer. Here is a simple example using a fixed-size buffer.

? Question description
- Producer thread : Continuously generate data and put it into the buffer.
- Consumer thread : fetches data from the buffer for processing.
- The buffer has a size limit and cannot be stored unlimitedly.
- It is necessary to prevent multiple threads from accessing the buffer (mutex) simultaneously.
- Producers cannot continue to produce when the buffer is full, and consumers cannot continue to consume when the buffer is empty (conditional synchronization).
? C sample code
#include <iostream> #include <thread> #include <mutex> #include <condition_variable> #include <queue> #include <vector> #include <chrono> #include <random> const int BUFFER_SIZE = 5; const int TOTAL_ITEMS = 20; std::queue<int> buffer; std::mutex mtx; std::condition_variable cv; bool finished = false; // Producer function void producer(int id) { std::random_device rd; std::mt19937 gen(rd()); std::uniform_int_distribution<> dis(100, 999); // Random number 100~999 for (int i = 0; i < TOTAL_ITEMS; i) { std::this_thread::sleep_for(std::chrono::milliseconds(dis(gen) % 200)); // Simulate production time int item = dis(gen); { std::unique_lock<std::mutex> lock(mtx); cv.wait(lock, []() { return buffer.size() < BUFFER_SIZE; }); buffer.push(item); std::cout << "Producer " << id << " produced: " << item << " (buffer size: " << buffer.size() << ")\n"; } // Automatically release the lock cv.notify_all(); // Notify consumers who may be blocking} } // Consumer function void consumer(int id) { while (true) { int item; { std::unique_lock<std::mutex> lock(mtx); // Wait: the buffer is not empty, or the production ends cv.wait(lock, []() { return !buffer.empty() || finished; }); if (buffer.empty() && finished) { break; // End consumer} item = buffer.front(); buffer.pop(); std::cout << "Consumer " << id << " consumed: " << item << " (buffer size: " << buffer.size() << ")\n"; } // Release the lock cv.notify_all(); // Notify the producer who may be blocking std::this_thread::sleep_for(std::chrono::milliseconds(300)); // Simulate consumption time} std::cout << "Consumer " << id << " finished.\n"; } int main() { std::vector<std::thread> producers; std::vector<std::thread> consumers; // Create 2 producers producers.emplace_back(producer, 1); producers.emplace_back(producer, 2); // Create 3 consumer consumers.emplace_back(consumer, 1); consumers.emplace_back(consumer, 2); consumers.emplace_back(consumer, 3); // Wait for all producers to complete for (auto& p : producers) { p.join(); } // After all producers are finished, set the finished flag { std::lock_guard<std::mutex> lock(mtx); finished = true; } cv.notify_all(); // Wait for all consumers to complete for (auto& c : consumers) { c.join(); } std::cout << "All tasks completed.\n"; return 0; }
? illustrate
- Buffer : Use
std::queue<int>
as the shared buffer. - Mutex
mtx
: Protect access tobuffer
. - Condition variable
cv
:- Producer waits for
buffer.size() < BUFFER_SIZE
- Consumers are waiting
!buffer.empty() || finished
- Producer waits for
-
finished
logo : Notify consumers that production has ended and avoid unlimited waiting. -
cv.notify_all()
: Wake up the waiting thread (althoughnotify_one
is sometimes more efficient,all
is safer).
? Output example (partial)
Producer 1 produced: 456 (buffer size: 1) Consumer 1 consumed: 456 (buffer size: 0) Producer 2 produced: 789 (buffer size: 1) Producer 1 produced: 123 (buffer size: 2) Consumer 2 consumed: 789 (buffer size: 1) ... Consumer 3 finished. All tasks completed.
? Key points summary
- Use
std::unique_lock
withcondition_variable::wait()
to achieve blocking and waiting. - Use lambda expressions to avoid false awakening in conditional judgment.
- The
finished
flag must be set inside the lock to ensure thread safety. - The consumer exits when it finds
finished
and the buffer is empty.
Basically that's it. This example shows how to implement a thread-safe producer-consumer model with modern C, suitable for learning multithreaded synchronization mechanisms.
The above is the detailed content of C producer consumer problem example. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

std::chrono is used in C to process time, including obtaining the current time, measuring execution time, operation time point and duration, and formatting analysis time. 1. Use std::chrono::system_clock::now() to obtain the current time, which can be converted into a readable string, but the system clock may not be monotonous; 2. Use std::chrono::steady_clock to measure the execution time to ensure monotony, and convert it into milliseconds, seconds and other units through duration_cast; 3. Time point (time_point) and duration (duration) can be interoperable, but attention should be paid to unit compatibility and clock epoch (epoch)

volatile tells the compiler that the value of the variable may change at any time, preventing the compiler from optimizing access. 1. Used for hardware registers, signal handlers, or shared variables between threads (but modern C recommends std::atomic). 2. Each access is directly read and write memory instead of cached to registers. 3. It does not provide atomicity or thread safety, and only ensures that the compiler does not optimize read and write. 4. Constantly, the two are sometimes used in combination to represent read-only but externally modifyable variables. 5. It cannot replace mutexes or atomic operations, and excessive use will affect performance.

There are mainly the following methods to obtain stack traces in C: 1. Use backtrace and backtrace_symbols functions on Linux platform. By including obtaining the call stack and printing symbol information, the -rdynamic parameter needs to be added when compiling; 2. Use CaptureStackBackTrace function on Windows platform, and you need to link DbgHelp.lib and rely on PDB file to parse the function name; 3. Use third-party libraries such as GoogleBreakpad or Boost.Stacktrace to cross-platform and simplify stack capture operations; 4. In exception handling, combine the above methods to automatically output stack information in catch blocks

In C, the POD (PlainOldData) type refers to a type with a simple structure and compatible with C language data processing. It needs to meet two conditions: it has ordinary copy semantics, which can be copied by memcpy; it has a standard layout and the memory structure is predictable. Specific requirements include: all non-static members are public, no user-defined constructors or destructors, no virtual functions or base classes, and all non-static members themselves are PODs. For example structPoint{intx;inty;} is POD. Its uses include binary I/O, C interoperability, performance optimization, etc. You can check whether the type is POD through std::is_pod, but it is recommended to use std::is_trivia after C 11.

To call Python code in C, you must first initialize the interpreter, and then you can achieve interaction by executing strings, files, or calling specific functions. 1. Initialize the interpreter with Py_Initialize() and close it with Py_Finalize(); 2. Execute string code or PyRun_SimpleFile with PyRun_SimpleFile; 3. Import modules through PyImport_ImportModule, get the function through PyObject_GetAttrString, construct parameters of Py_BuildValue, call the function and process return

FunctionhidinginC occurswhenaderivedclassdefinesafunctionwiththesamenameasabaseclassfunction,makingthebaseversioninaccessiblethroughthederivedclass.Thishappenswhenthebasefunctionisn’tvirtualorsignaturesdon’tmatchforoverriding,andnousingdeclarationis

AnullpointerinC isaspecialvalueindicatingthatapointerdoesnotpointtoanyvalidmemorylocation,anditisusedtosafelymanageandcheckpointersbeforedereferencing.1.BeforeC 11,0orNULLwasused,butnownullptrispreferredforclarityandtypesafety.2.Usingnullpointershe

In C, there are three main ways to pass functions as parameters: using function pointers, std::function and Lambda expressions, and template generics. 1. Function pointers are the most basic method, suitable for simple scenarios or C interface compatible, but poor readability; 2. Std::function combined with Lambda expressions is a recommended method in modern C, supporting a variety of callable objects and being type-safe; 3. Template generic methods are the most flexible, suitable for library code or general logic, but may increase the compilation time and code volume. Lambdas that capture the context must be passed through std::function or template and cannot be converted directly into function pointers.
