web-dev-qa-db-fra.com

Quand utiliser les variables de condition pthread?

pthread question:

il semble qu'une variable de condition ne fonctionne que si pthread_cond_wait est appelé avant que l'autre thread appelle pthread_cond_notify. Si la notification se produit avant l'attente, l'attente sera bloquée.

Ma question est: quand faut-il utiliser les variables de condition?

Le planificateur peut préempter les threads et une notification peut se produire avant l'attente.

Attendre sur des sémaphores n'a pas ce problème - ceux-ci ont un compteur.

Quand une variable conditionnelle est-elle meilleure qu'un sémaphore?

Voici un test:

**** file condvar.c

#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>

// ******
// test of conditional variables;
// if cond-var is notified before wait starts, then wait never wakes up !!!
// better to use semaphores than this crap.
// ******

pthread_mutex_t cond_var_lock =  PTHREAD_MUTEX_INITIALIZER; 
pthread_cond_t cond_var = PTHREAD_COND_INITIALIZER;

int wait_first = 1;

void *tfunc(void *arg)
{
(void) arg;

if (!wait_first)
    sleep(1);

fprintf(stderr,"on enter cond_var_lock %lx\n", pthread_self());
pthread_mutex_lock( &cond_var_lock);
fprintf(stderr,"before pthread_cond_wait %lx\n", pthread_self());
pthread_cond_wait( &cond_var, &cond_var_lock);
fprintf(stderr,"after pthread_cond_wait %lx\n", pthread_self());
pthread_mutex_unlock( &cond_var_lock);
fprintf(stderr,"after exit cond_var_lock %lx\n", pthread_self());

return 0;
}

int main(int argc, char *argv[])
{
pthread_t th;

if (argc > 0) 
    wait_first = atoi( argv[1] );

if (wait_first)
{
    fprintf(stderr,"********* Wait first ***********\n");
} else {
    fprintf(stderr,"********* Notify first *********\n");
}


pthread_create( &th, 0, tfunc, 0 );

if (wait_first)
{
    sleep(1);
} 

fprintf(stderr, "! on enter cond_var_lock %lx\n", pthread_self());
pthread_mutex_lock( &cond_var_lock);
fprintf(stderr, "! before pthread_cond_signal %lx\n", pthread_self());
pthread_cond_signal( &cond_var );
fprintf(stderr, "! after pthread_cond_signal %lx\n", pthread_self());
pthread_mutex_unlock( &cond_var_lock);
fprintf(stderr, "! after exit cond_var_lock %lx\n", pthread_self());

sleep(5);
return 0;    
}

**** file test.sh

#!/bin/sh

set -e
set -x

gcc condvar.c -o condvar -lpthread

./condvar 1

./condvar 0

**** test output

Output:

+ gcc condvar.c -o condvar -lpthread
+ ./condvar 1
********* Wait first ***********
on enter cond_var_lock b7779b70
before pthread_cond_wait b7779b70
! on enter cond_var_lock b777a6c0
! before pthread_cond_signal b777a6c0
! after pthread_cond_signal b777a6c0
! after exit cond_var_lock b777a6c0
after pthread_cond_wait b7779b70
after exit cond_var_lock b7779b70
+ ./condvar 0
********* Notify first *********
! on enter cond_var_lock b785c6c0
! before pthread_cond_signal b785c6c0
! after pthread_cond_signal b785c6c0
! after exit cond_var_lock b785c6c0
on enter cond_var_lock b785bb70
before pthread_cond_wait b785bb70
clinuxpthreads
17
MichaelMoser

Les variables de condition doivent être utilisées pour attendre et être notifiées. Ils ne sont pas la condition elle-même et ce ne sont pas des événements. La condition est contenue dans la logique de programmation environnante. Le modèle d'utilisation typique des variables de condition est

// safely examine the condition, prevent other threads from
// altering it
pthread_mutex_lock (&lock);
while ( SOME-CONDITION is false)
    pthread_cond_wait (&cond, &lock);

// Do whatever you need to do when condition becomes true
do_stuff();
pthread_mutex_unlock (&lock);

D'un autre côté, un thread, signalant la variable de condition, ressemble généralement à

// ensure we have exclusive access to whathever comprises the condition
pthread_mutex_lock (&lock);

ALTER-CONDITION

// Wakeup at least one of the threads that are waiting on the condition (if any)
pthread_cond_signal (&cond);

// allow others to proceed
pthread_mutex_unlock (&lock)
44
chill