Click here to Skip to main content
15,861,168 members
Articles / Programming Languages / C++

Introduction to Multi-threaded Code

Rate me:
Please Sign up or sign in to vote.
4.84/5 (55 votes)
26 Mar 2000CPOL 402K   14.4K   182   55
Synchronizing worker threads using 3 different methods

Introduction

Someone recently asked me what I recommend for synchronizing worker threads and I suggested setting an event. This person's response was that you could not do that since worker threads do not support a message pump (UI threads are required to support messages). The confusion here is that events and messages are different animals under windows.

I have forgotten where I originally copied these examples, but I found them to be interesting because of their simplicity. If anyone is aware of the author of this code, I would appreciate hearing from you, so I can give him/her credit.

Note that there is considerable support for threads in MFC that is not covered here. APIs like _beginthread (a C runtime library call) would likely be replaced by MFC APIs like AfxBeginThread in an MFC application.

No Synchronization

This first example illustrates two unsynchronized threads. The main loop, which is the primary thread of a process, prints the contents of a global array of integers. The thread called "Thread" continuously populates the global array of integers.

C++
#include <process.h>
#include <stdio.h>

int a[ 5 ];

void Thread( void* pParams )
{ int i, num = 0;

  while ( 1 )
  {
     for ( i = 0; i < 5; i++ ) a[ i ] = num;
     num++;
  }
}

int main( void )
{
   _beginthread( Thread, 0, NULL );

   while( 1 )
      printf("%d %d %d %d %d\n",
             a[ 0 ], a[ 1 ], a[ 2 ],
             a[ 3 ], a[ 4 ] );

 return 0;
}

Note in this sample output, the numbers in red illustrate a state where the primary thread preempted the secondary thread in the middle of populating the values of the array:

81751652 81751652 81751651 81751651 81751651
81751652 81751652 81751651 81751651 81751651
83348630 83348630 83348630 83348629 83348629
83348630 83348630 83348630 83348629 83348629
83348630 83348630 83348630 83348629 83348629

If you are running Windows 9x/NT/2000, you can run this program by clicking here. After the program begins to run, press the "Pause" key, stop the display output (this stops the primary thread's I/O, but the secondary thread continues to run in the background) and any other key to restart it.

Critical Section Objects

What if your main thread needed all elements of the array to processed prior to reading? One solution is to use a critical section.

Critical section objects provide synchronization similar to that provided by mutex objects, except critical section objects can be used only by the threads of a single process. Event, mutex, and semaphore objects can also be used in a single-process application, but critical section objects provide a slightly faster, more efficient mechanism for mutual-exclusion synchronization. Like a mutex object, a critical section object can be owned by only one thread at a time, which makes it useful for protecting a shared resource from simultaneous access. There is no guarantee about the order in which threads will obtain ownership of the critical section, however, the system will be fair to all threads.

C++
#include <windows.h>
#include <process.h>
#include <stdio.h>

CRITICAL_SECTION cs;
int a[ 5 ];

void Thread( void* pParams )
{
  int i, num = 0;

  while ( TRUE )
  {
     EnterCriticalSection( &cs );
     for ( i = 0; i < 5; i++ ) a[ i ] = num;
     LeaveCriticalSection( &cs );
     num++;
  }
}

int main( void )

{
  InitializeCriticalSection( &cs );
  _beginthread( Thread, 0, NULL );

  while( TRUE )
  {
     EnterCriticalSection( &cs );
     printf( "%d %d %d %d %d\n",
             a[ 0 ], a[ 1 ], a[ 2 ],
             a[ 3 ], a[ 4 ] );
     LeaveCriticalSection( &cs );
  }
  return 0;
}

If you are running Windows 9x/NT/2000, you can run this program by clicking here.

Mutex Objects

A mutex object is a synchronization object whose state is set to signaled when it is not owned by any thread, and non-signaled when it is owned. Only one thread at a time can own a mutex object, whose name comes from the fact that it is useful in coordinating mutually exclusive access to a shared resource. For example, to prevent two threads from writing to shared memory at the same time, each thread waits for ownership of a mutex object before executing the code that accesses the memory. After writing to the shared memory, the thread releases the mutex object.

Two or more processes can call CreateMutex to create the same named mutex. The first process actually creates the mutex, and subsequent processes open a handle to the existing mutex. This enables multiple processes to get handles of the same mutex, while relieving the user of the responsibility of ensuring that the creating process is started first. When using this technique, you should set the bInitialOwner flag to FALSE; otherwise, it can be difficult to be certain which process has initial ownership.

Multiple processes can have handles of the same mutex object, enabling use of the object for interprocess synchronization. The following object-sharing mechanisms are available:

  • A child process created by the CreateProcess function can inherit a handle to a mutex object if the lpMutexAttributes parameter of CreateMutex enabled inheritance.
  • A process can specify the mutex-object handle in a call to the DuplicateHandle function to create a duplicate handle that can be used by another process.
  • A process can specify the name of a mutex object in a call to the OpenMutex or CreateMutex function.

Generally speaking, if you are synchronizing threads within the same process, a critical section object is more efficient.

C++
#include <windows.h>
#include <process.h>
#include <stdio.h>

HANDLE hMutex;
int a[ 5 ];

void Thread( void* pParams )
{
   int i, num = 0;

   while ( TRUE )
   {
      WaitForSingleObject( hMutex, INFINITE );
      for ( i = 0; i < 5; i++ ) a[ i ] = num;
      ReleaseMutex( hMutex );
      num++;
   }
}

int main( void )
{
   hMutex = CreateMutex( NULL, FALSE, NULL );
   _beginthread( Thread, 0, NULL );

   while( TRUE )

   {
      WaitForSingleObject( hMutex, INFINITE );
      printf( "%d %d %d %d %d\n",
              a[ 0 ], a[ 1 ], a[ 2 ],
              a[ 3 ], a[ 4 ] );
      ReleaseMutex( hMutex );
   }
   return 0;
}

If you are running Windows 9x/NT/2000, you can run this program by clicking here.

Event Objects

What if we want to force the secondary thread to run each time the primary thread finishes printing the contents of the global array, so that the values in each line of output is only incremented by one?

An event object is a synchronization object whose state can be explicitly set to signaled by use of the SetEvent or PulseEvent function. Following are the two types of event object.

Object Description
Manual-reset event An event object whose state remains signaled until it is explicitly reset to non-signaled by the ResetEvent function. While it is signaled, any number of waiting threads, or threads that subsequently specify the same event object in one of the wait functions, can be released.
Auto-reset event An event object whose state remains signaled until a single waiting thread is released, at which time the system automatically sets the state to non-signaled. If no threads are waiting, the event object's state remains signaled.

The event object is useful in sending a signal to a thread indicating that a particular event has occurred. For example, in overlapped input and output, the system sets a specified event object to the signaled state when the overlapped operation has been completed. A single thread can specify different event objects in several simultaneous overlapped operations, then use one of the multiple-object wait functions to wait for the state of any one of the event objects to be signaled.

A thread uses the CreateEvent function to create an event object. The creating thread specifies the initial state of the object and whether it is a manual-reset or auto-reset event object. The creating thread can also specify a name for the event object. Threads in other processes can open a handle to an existing event object by specifying its name in a call to the OpenEvent function. For additional information about names for mutex, event, semaphore, and timer objects, see Interprocess Synchronization.

A thread can use the PulseEvent function to set the state of an event object to signaled and then reset it to non-signaled after releasing the appropriate number of waiting threads. For a manual-reset event object, all waiting threads are released. For an auto-reset event object, the function releases only a single waiting thread, even if multiple threads are waiting. If no threads are waiting, PulseEvent simply sets the state of the event object to non-signaled and returns.

C++
#include <windows.h>
#include <process.h>
#include <stdio.h>

HANDLE hEvent1, hEvent2;
int a[ 5 ];

void Thread( void* pParams )
{
   int i, num = 0;

   while ( TRUE )
   {
      WaitForSingleObject( hEvent2, INFINITE );
      for ( i = 0; i < 5; i++ ) a[ i ] = num;
      SetEvent( hEvent1 );
      num++;
   }
}

int main( void )
{
   hEvent1 = CreateEvent( NULL, FALSE, TRUE, NULL );
   hEvent2 = CreateEvent( NULL, FALSE, FALSE, NULL );

   _beginthread( Thread, 0, NULL );

   while( TRUE )
   {
      WaitForSingleObject( hEvent1, INFINITE );
      printf( "%d %d %d %d %d\n",
              a[ 0 ], a[ 1 ], a[ 2 ],
              a[ 3 ], a[ 4 ] );
      SetEvent( hEvent2 );
   }
   return 0;
}

If you are running Windows 9x/NT/2000, you can run this program by clicking here.

Summary of Synchronization Objects

The MSDN News for July/August 1998 has a front page article on Synchronization Objects. The following table is from that article:

Name Relative speed Cross process Resource counting Supported platforms
Critical Section Fast No No (exclusive access) 9x/NT/CE
Mutex Slow Yes No (exclusive access) 9x/NT/CE
Semaphore Slow Yes Automatic 9x/NT
Event Slow Yes Yes 9x/NT/CE
Metered Section Fast Yes Automatic 9x/NT/CE

License

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


Written By
Software Developer (Senior) Retired
United States United States
I am currently retired, but spent the last 40 years of my career writing software for MS-DOS and Windows (starting with Windows 1.0).

My first experience with software was writing assembly code for the Motorola 6800.

During the S100 bus days, I wrote 8080 assembly and Basic.

With the introduction of the IBM PC I wrote in Borland Pascal for MS-DOS.

When Microsoft introduced Windows 1.0 I started writing in C code.

For the majority of my career, I did development in C++ starting with Visual C++ 1.0.

Some of my development was in .NET, but it never appealed to me like C++.

Comments and Discussions

 
GeneralMy vote of 2 Pin
Matra Divat21-Mar-13 4:04
Matra Divat21-Mar-13 4:04 
QuestionCritical Section Objects example: editing proposal Pin
Stefano Capelli8-Nov-12 6:04
professionalStefano Capelli8-Nov-12 6:04 
QuestionGood Article Pin
srikanth_shettigar22-Mar-12 17:25
srikanth_shettigar22-Mar-12 17:25 
Questionmy 5 Pin
marc ochsenmeier22-Jan-12 6:01
marc ochsenmeier22-Jan-12 6:01 
GeneralMy vote of 5 Pin
Pranit Kothari26-Dec-11 15:56
Pranit Kothari26-Dec-11 15:56 
Generalthanks Pin
cute_friend707725-Feb-10 0:52
cute_friend707725-Feb-10 0:52 
Generalthanks Pin
cute_friend707725-Feb-10 0:52
cute_friend707725-Feb-10 0:52 
QuestionDoes it work in Linux system? Pin
C Is Sharp25-Jan-10 21:25
C Is Sharp25-Jan-10 21:25 
QuestionEvent Object Pin
Mahmoud Fayez31-Oct-07 2:33
Mahmoud Fayez31-Oct-07 2:33 
GeneralExecuting Two Functions Simultaneously Pin
Ms. Agrawal1-Apr-07 20:55
Ms. Agrawal1-Apr-07 20:55 
GeneralSynchronization Pin
Abhitha25-Mar-07 23:18
Abhitha25-Mar-07 23:18 
QuestionProblem Thread synchronization using Events Pin
Muralish15-Sep-06 19:40
Muralish15-Sep-06 19:40 
QuestionA little question about the source code above [modified] Pin
HDZ@CN27-Jun-06 16:16
HDZ@CN27-Jun-06 16:16 
GeneralGlobal Mutex Problem Pin
DavidLoeb8-Jun-06 19:34
DavidLoeb8-Jun-06 19:34 
GeneralThanx - Suggestion Pin
Osama E. Adly29-Mar-06 3:16
Osama E. Adly29-Mar-06 3:16 
GeneralHandles leak Pin
Anthony_Yio19-Nov-04 16:15
Anthony_Yio19-Nov-04 16:15 
Generalvc++ Pin
Anonymous19-Oct-03 0:35
Anonymous19-Oct-03 0:35 
GeneralRe: vc++ Pin
Selvam R5-Feb-04 23:18
professionalSelvam R5-Feb-04 23:18 
GeneralRe: vc++ Pin
Larry Dobson17-Jun-04 3:29
Larry Dobson17-Jun-04 3:29 
GeneralThanks for Event Objects Pin
Moak16-Mar-03 11:14
Moak16-Mar-03 11:14 
GeneralRe: Thanks for Event Objects Pin
William T. Block16-Mar-03 18:18
William T. Block16-Mar-03 18:18 
QuestionCan not compile Pin
Emiliano5-Mar-03 13:47
Emiliano5-Mar-03 13:47 
AnswerRe: Can not compile Pin
Peter Hancock5-Mar-03 13:58
Peter Hancock5-Mar-03 13:58 
Generalwhy this code doesn't work Pin
Anonymous7-Dec-02 9:46
Anonymous7-Dec-02 9:46 
GeneralRe: why this code doesn't work Pin
Selvam R19-Feb-04 22:53
professionalSelvam R19-Feb-04 22:53 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.