【发布时间】:2014-01-13 09:07:15
【问题描述】:
pthread问题:
似乎只有在其他线程调用 pthread_cond_notify 之前调用 pthread_cond_wait 时,条件变量才有效。 如果在等待之前以某种方式发生通知,则等待将被卡住。
我的问题是:什么时候应该使用条件变量?
调度程序可以抢占线程,并且在等待之前可能会发生通知。
等待信号量没有这个问题——它们有一个计数器。
什么时候条件变量比信号量好?
这是一个测试:
文件 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;
}
文件 test.sh
#!/bin/sh
set -e
set -x
gcc condvar.c -o condvar -lpthread
./condvar 1
./condvar 0
测试输出
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
【问题讨论】:
-
补充:i如果你在旧 glibc(2.5 之前)的系统上运行,那么信号量会出现竞争条件,有时会导致内存损坏sourceware.org/bugzilla/show_bug.cgi?id=12674