Subj : Re: pthread_cond_signal() semantics
To   : comp.programming.threads
From : Markus Elfring
Date : Mon Jan 10 2005 10:39 pm

> 1) pthread_cond_signal(&cond) simply marks the waiting thread as waiting
on
> the mutex ( as if it had just called pthread_mutex_lock() and not
> pthread_cond_wait() ).
>
> 2) pthread_mutex_unlock(&mutex) merely unlocks the mutex, allowing the
> thread to reaquire the lock before the waiting thread can do so.

Do the following links point to useful background informations for you?

1. unlock cond before signal?

http://groups.google.de/groups?threadm=Wk%25qd.3639%24dL1.953%40news.cpqcorp
..net

2. A word of caution when juggling pthread_cond_signal/pthread_mutex_unlock

http://groups.google.de/groups?threadm=d976b79f.0403182115.45c8fed4%40postin
g.google.com

3. spurious wakeup

http://groups.google.de/groups?threadm=40ed1d8f.0411191313.4dff837c@posting.
google.com

4. pthread_cond_* implementation questions
   http://groups.google.de/groups?threadm=3A70296F.B651AE34%40compaq.com

5. An easy one

http://groups.google.de/groups?threadm=3354752c.103083005%40funnelweb.surf.d
ascom.com

6. difference between mutex and condition

http://groups.google.de/groups?threadm=T18K7.1705%24RL6.56824%40news.cpqcorp
..net

Regards,
Markus

.