MUTEX_IS_LOCKED(9) Mutex API reference MUTEX_IS_LOCKED(9)NAME
mutex_is_locked - is the mutex locked
int mutex_is_locked(struct mutex * lock);
the mutex to be queried
Returns 1 if the mutex is locked, 0 if unlocked.
Rusty Russell <firstname.lastname@example.org>
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 MUTEX_IS_LOCKED(9)
Check Out this Related Man Page
pthread_mutex_lock(3) Library Functions Manual pthread_mutex_lock(3)NAME
pthread_mutex_lock - Locks an unlocked mutex.
DECthreads POSIX 1003.1c Library (libpthread.so)
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
Mutex to be locked.
This routine locks a mutex with behavior that depends upon the type of mutex, as follows: If a normal or default mutex is specified, a
deadlock can result if the current owner of the mutex calls this routine in an attempt to lock the mutex a second time. (The deadlock is
not detected or reported.) If a recursive mutex is specified, the current owner of the mutex can relock the same mutex without blocking.
The lock count is incremented for each recursive lock within the thread. If an errorcheck mutex is specified and the current owner tries
to lock the mutex a second time, this routine reports the [EDEADLK] error. If the mutex is locked by another thread, the calling thread
waits for the mutex to become available.
Use the pthread_mutexattr_settype(3) routine to set the type of the mutex to normal, default, recursive, or errorcheck. For more informa-
tion about types of mutexes, see the desciption of pthread_mutexattr_settype(3).
The thread that has locked a mutex becomes its current owner and remains its owner until the same thread has unlocked it. This routine
returns with the mutex in the locked state and with the current thread as the mutex's current owner.
A recursive or errorcheck mutex records the identity of the thread that locks it, allowing debuggers to display this information. In most
cases, normal and default mutexes do not record the owning thread's identity.
If an error condition occurs, this routine returns an integer value indicating the type of error. Possible return values are as follows:
Successful completion. A deadlock condition is detected. The value specified by mutex is not a valid mutex.
Functions: pthread_mutexattr_settype(3), pthread_mutex_destroy(3), pthread_mutex_init(3), pthread_mutex_trylock(3), pthread_mutex_unlock(3)
Manuals: Guide to DECthreads and Programmer's Guide
My application gets hang at the popen statement in Soalris 5.8. While debugging I found that it halts at _lwp_sema_wait. After googling I have added /usr/lib/lwp in the LD_LIBRARY_PATH and now it halts at lwp_park. Please help me what I need to do to solve this issue. The application runs... (6 Replies)
I am trying the understand the conditional variable concept.
I went through the following site:
I understand that condition variables allow threads to synchronize based upon the VALUE of data.
When the data acheives a particular... (2 Replies)
How to write a class that can only be instancialized once?
what about my implementation below?
using namespace std;
static int num;
int Singleton::num = 1; (10 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
My problem is that when creating my producers and consumers, if I don't create an equal number of both, the... (12 Replies)