Thread operations share a little share of variables.

Some time ago in order to solve the VoLTE's T-side short Message flow problem, I wrote a T-side short message tool, on the base thread to engage 3 threads. Because the company's executive machine is more than 4 cores of virtual machines, so the number of threads is completely fine.

The thread created at the start of the program is used for maintenance, such as how many messages are received, how many messages are sent, and what kind of messages are there.

Thread 1 is used to receive the message, the message is not dry, the direct turn into a string is thrown into the message queue.

Thread 2 is used to process messages, primarily to differentiate the message type, then generate the message that needs to be returned and throw it into the message queue.

Thread 3 is used to send messages, what happens in the message queue.

There is a shared data interaction between three threads, mainly in the processing of message queues. Message Queuing does not use any special protection mechanism at the time of processing, so the vector can be handled normally. Occasionally, however, there is a case where the program exits unexpectedly. The program architecture is relatively simple and should not have any problems. The handling of billions of news has not seen anything unusual.

So for the program to quit the problem, now suspect that the point is vector thread security.

To this problem, looked at the core programming, think of a kind of manual lock, Simple is to use the volatile variable memory real-time characteristics, manually add a lock. When the lock is applied to determine if it is true, the loop lock is entered as true, and the exit is not true.

A simple lock on the variable is done in this way, and if the data is being processed, wait a minute.

But in this way, it is more worrying if it is not an atomic command, such as a volatile variable set to 1 requires the execution of 3 assembly instructions, a multi-core processor may have a minimum probability of the fight event, are locked.

Thread operations share a little share of variables.