Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pthread_rwlock_unlock(3) [freebsd man page]

PTHREAD_RWLOCK_UNLOCK(3)				   BSD Library Functions Manual 				  PTHREAD_RWLOCK_UNLOCK(3)

NAME
pthread_rwlock_unlock -- release a read/write lock LIBRARY
POSIX Threads Library (libpthread, -lpthread) SYNOPSIS
#include <pthread.h> int pthread_rwlock_unlock(pthread_rwlock_t *lock); DESCRIPTION
The pthread_rwlock_unlock() function is used to release the read/write lock previously obtained by pthread_rwlock_rdlock(), pthread_rwlock_wrlock(), pthread_rwlock_tryrdlock(), or pthread_rwlock_trywrlock(). RETURN VALUES
If successful, the pthread_rwlock_unlock() function will return zero. Otherwise an error number will be returned to indicate the error. The results are undefined if lock is not held by the calling thread. ERRORS
The pthread_rwlock_unlock() function may fail if: [EINVAL] The value specified by lock is invalid. [EPERM] The current thread does not own the read/write lock. SEE ALSO
pthread_rwlock_rdlock(3), pthread_rwlock_wrlock(3) STANDARDS
The pthread_rwlock_unlock() function is expected to conform to Version 2 of the Single UNIX Specification (``SUSv2''). HISTORY
The pthread_rwlock_unlock() function first appeared in FreeBSD 3.0. BSD
August 4, 1998 BSD

Check Out this Related Man Page

PTHREAD_RWLOCK_RDLOCK(3)				   BSD Library Functions Manual 				  PTHREAD_RWLOCK_RDLOCK(3)

NAME
pthread_rwlock_rdlock, pthread_rwlock_tryrdlock -- acquire a read/write lock for reading LIBRARY
POSIX Threads Library (libpthread, -lpthread) SYNOPSIS
#include <pthread.h> int pthread_rwlock_rdlock(pthread_rwlock_t *lock); int pthread_rwlock_tryrdlock(pthread_rwlock_t *lock); DESCRIPTION
The pthread_rwlock_rdlock() function acquires a read lock on lock provided that lock is not presently held for writing and no writer threads are presently blocked on the lock. If the read lock cannot be immediately acquired, the calling thread blocks until it can acquire the lock. The pthread_rwlock_tryrdlock() function performs the same action, but does not block if the lock cannot be immediately obtained (i.e., the lock is held for writing or there are waiting writers). A thread may hold multiple concurrent read locks. If so, pthread_rwlock_unlock() must be called once for each lock obtained. The results of acquiring a read lock while the calling thread holds a write lock are undefined. IMPLEMENTATION NOTES
To prevent writer starvation, writers are favored over readers. RETURN VALUES
If successful, the pthread_rwlock_rdlock() and pthread_rwlock_tryrdlock() functions will return zero. Otherwise an error number will be returned to indicate the error. ERRORS
The pthread_rwlock_tryrdlock() function will fail if: [EBUSY] The lock could not be acquired because a writer holds the lock or was blocked on it. The pthread_rwlock_rdlock() and pthread_rwlock_tryrdlock() functions may fail if: [EAGAIN] The lock could not be acquired because the maximum number of read locks against lock has been exceeded. [EDEADLK] The current thread already owns lock for writing. [EINVAL] The value specified by lock is invalid. [ENOMEM] Insufficient memory exists to initialize the lock (applies to statically initialized locks only). SEE ALSO
pthread_rwlock_init(3), pthread_rwlock_trywrlock(3), pthread_rwlock_unlock(3), pthread_rwlock_wrlock(3) STANDARDS
The pthread_rwlock_rdlock() and pthread_rwlock_tryrdlock() functions are expected to conform to Version 2 of the Single UNIX Specification (``SUSv2''). HISTORY
The pthread_rwlock_rdlock() function first appeared in FreeBSD 3.0. BSD
August 4, 1998 BSD
Man Page

3 More Discussions You Might Find Interesting

1. Programming

__throw

Hi All, We are fixing an application, and to do this we've used GDB. We have a coredump file, therefore we can print a backtrace and watch the variables content at the moment of the crash. This is the outcome of bt gd command: 0 0x0ffab7dc in __pthread_rwlock_unlock (rwlock=0x109db640)... (1 Reply)
Discussion started by: lagigliaivan
1 Replies

2. Programming

Deallocating memory in multi-threaded environment.

I'm having a hard time figuring out how to manage deallocation of memory in multithreaded environments. Specifically what I'm having a hard time with is using a lock to protect a structure, but when it's time to free the structure, you have to unlock the lock to destroy the lock itself. Which will... (5 Replies)
Discussion started by: gngrwzrd
5 Replies

3. Programming

Thread parameter in ANSI C makes a segmentation fault

The creation of thread. void Client_Constructor ( const char* IPAddr ) { pthread_t tid; pthread_attr_t rx; /* Create separate memory for client argument */ struct ThreadArgs *threadArgs; if ( ( threadArgs = ( struct ThreadArgs* ) malloc( sizeof( struct ThreadArgs )... (14 Replies)
Discussion started by: sehang
14 Replies