Scribd
Upload
89 views2 pages

Concurrent Programming

This document discusses concurrent programming issues and strategies for developing multithreaded programs. It provides examples of common synchronization primitives like locks and condition variables. It recommends encapsulating shared state within objects and identifying units of concurrency as threads. A complete example of a readers-writers problem solution is presented using locks and condition variables to coordinate access to a shared database between reader and writer threads. General coding practices are outlined such as acquiring locks at procedure beginnings and releases at ends.

Uploaded by

poojajadhav
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
89 views2 pages

Concurrent Programming

This document discusses concurrent programming issues and strategies for developing multithreaded programs. It provides examples of common synchronization primitives like locks and condition variables. It recommends encapsulating shared state within objects and identifying units of concurrency as threads. A complete example of a readers-writers problem solution is presented using locks and condition variables to coordinate access to a shared database between reader and writer threads. General coding practices are outlined such as acquiring locks at procedure beginnings and releases at ends.

Uploaded by

poojajadhav
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Summary of Our Discussions

Developing and debugging concurrent programs is hard


Non-deterministic interleaving of instructions

Concurrent Programming Issues: Summary

Synchronization constructs
Locks: mutual exclusion Condition variables: conditional synchronization Other primitives:
v

Semaphores
u u

Binary vs. counting Can be used for mutual exclusion and conditional synchronization

How can you use these constructs effectively?


Develop and follow strict programming style/strategy

Programming Strategy
Decompose the problem into objects Object-oriented style of programming
Identify shared chunk of state Encapsulate shared state and synchronization variables inside objects

General Programming Strategy


Two step process Threads:
Identify units of concurrency these are your threads Identify chunks of shared state make each shared thing an object; identify methods for these objects (how will the thread access the objects?) Write down the main loop for the thread

Dont manipulate shared variables or synchronization variables along with the logic associated with a thread

Shared objects:
Identify synchronization constructs
v

Mutual exclusion vs. conditional synchronization

Create a lock/condition variable for each constraint Develop the methods using locks and condition variables for coordination

Coding Style and Standards


Always do things the same way Always use locks and condition variables Always hold locks while operating on condition variables Always acquire lock at the beginning of a procedure and release it at the end
If it does not make sense to do this split your procedures further

Readers/Writers: A Complete Example


Motivation
Shared databases accesses
v

Examples: bank accounts, airline seats,

Two types of users


Readers: Never modify data Writers: read and modify data

Always use while to check conditions, not if


while (predicate on state variable) {{ while (predicate on state variable) conditionVariablewait(&lock); conditionVariablewait(&lock); }; };

Problem constraints
Using a single lock is too restrictive
v v

Allow multiple readers at the same time but only one writer at any time Readers can access database when there are no writers Writers can access database when there are no readers/writers Only one thread can manipulate shared variables at any time
6

Specific constraints
v v v
5

(Almost) never sleep() in your code


Use condition variables to synchronize

Readers/Writer: Solution Structure


Basic structure: two methods
Database::Read() {{ Database::Read() Wait until no writers; Wait until no writers; Access database; Access database; check out wake up waiting writers; check out wake up waiting writers; }}

Database::Write() {{ Database::Write() Wait until no readers/writers; Wait until no readers/writers; Access database; Access database; check out wake up waiting readers/writers; check out wake up waiting readers/writers; }} AR ==0; // # of active readers AR 0; // # of active readers AW ==0; // # of active writers AW 0; // # of active writers WR ==0; // # of waiting readers WR 0; // # of waiting readers WW ==0; // # of waiting writers WW 0; // # of waiting writers Condition okToRead; Condition okToRead; Condition okToWrite; Condition okToWrite; Lock lock; Lock lock;

State variables

You might also like