From 7d9196d329877a5daad99c73aec57dc606076a56 Mon Sep 17 00:00:00 2001 From: patacongo Date: Sat, 31 May 2008 18:14:02 +0000 Subject: Comments updated git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@755 42af7a65-404d-4744-a932-0658087f49c3 --- nuttx/sched/pthread_mutexunlock.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/nuttx/sched/pthread_mutexunlock.c b/nuttx/sched/pthread_mutexunlock.c index 4551c729f..e98526311 100644 --- a/nuttx/sched/pthread_mutexunlock.c +++ b/nuttx/sched/pthread_mutexunlock.c @@ -73,7 +73,14 @@ * Function: pthread_mutex_unlock * * Description: - * Unlock a mutex. + * The pthread_mutex_unlock() function releases the mutex object referenced + * by mutex. The manner in which a mutex is released is dependent upon the + * mutex's type attribute. If there are threads blocked on the mutex object + * referenced by mutex when pthread_mutex_unlock() is called, resulting in + * the mutex becoming available, the scheduling policy is used to determine + * which thread shall acquire the mutex. (In the case of PTHREAD_MUTEX_RECURSIVE + * mutexes, the mutex becomes available when the count reaches zero and the + * calling thread no longer has any locks on this mutex). * * If a signal is delivered to a thread waiting for a mutex, upon return from * the signal handler the thread resumes waiting for the mutex as if it was -- cgit v1.2.3