How to synchronize a bool/int variable that is getting used by two threads

Question

0.00/5 (No votes)

See more:

Hello Guys,

I know its very simple and basic question thought would like to know answer.
I am newbie in threading concepts.

Question: Suppose, I have a bool variable lets say bool var, Two threads can use this variable.

How should I synchronize it?

As per my knowledge goes,we can use mutex to lock variable. This will ensure that when a variable is getting used by a thread, other thread will can not access it.

What are other solutions.

Please help.

Regards,
Joy

Posted 23-Apr-14 20:19pm

joyjhonson

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pablo Aliskevicius · Answer 1 · 2014-04-23T22:32:00

Consider using "The scoped locking idiom". It is described (among many other places) at http://www.cs.wustl.edu/~schmidt/PDF/ScopedLocking.pdf[^]

In general, you need:
1. A class that encapsulates your shared resource.
2. All public functions in the class acquire a lock at entry, and release it at exit, possibly using the aforementioned idiom.

In Windows, the API exposes some functions to avoid the overhead for simple cases: for instance, OverlockedIncrement and OverlockedDecrement for integers.

If it's important for you, google also "lock free threading patterns".

Hope this helps,

Pablo.