pthread_rwlockattr_getkind_np(3) [linux man page]

PTHREAD_RWLOCKATTR_SETKIND_NP(3)			     Library Functions Manual				  PTHREAD_RWLOCKATTR_SETKIND_NP(3)

NAME

       pthread_rwlockattr_setkind_np,  pthread_rwlockattr_getkind_np  -  set/get  the read-write lock kind of the thread read-write lock attribute
       object

SYNOPSIS

       #include <pthread.h>

       int pthread_rwlockattr_setkind_np(pthread_rwlockattr_t *attr,
					  int pref);
       int pthread_rwlockattr_getkind_np(const pthread_rwlockattr_t *attr,
					  int *pref);

       Compile and link with -pthread.

   Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

       pthread_rwlockattr_setkind_np(), pthread_rwlockattr_getkind_np():
	   _XOPEN_SOURCE >= 500 || _POSIX_C_SOURCE >= 200809L

DESCRIPTION

       The pthread_rwlockattr_setkind_np() function sets the "lock kind" attribute of the read-write lock attribute object referred to by attr	to
       the value specified in pref.  The argument pref may be set to one of the following:

       PTHREAD_RWLOCK_PREFER_READER_NP
	      This is the default.  A thread may hold multiple read locks; that is, read locks are recursive.  According to The Single Unix Speci-
	      fication, the behavior is unspecified when a reader tries to place a lock, and there is no write lock but writers are waiting.  Giv-
	      ing preference to the reader, as is set by PTHREAD_RWLOCK_PREFER_READER_NP, implies that the reader will receive the requested lock,
	      even if a writer is waiting.  As long as there are readers, the writer will be starved.

       PTHREAD_RWLOCK_PREFER_WRITER_NP
	      This is intended as the write lock analog of PTHREAD_RWLOCK_PREFER_READER_NP.  But see BUGS.

       PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP
	      Setting the lock kind to this avoids writer starvation as long as any read locking is not done in a recursive fashion.

       The pthread_rwlockattr_getkind_np() function returns the value of the lock kind attribute of the read-write lock attribute object  referred
       to by attr in the pointer pref.

RETURN VALUE

       On  success,  these  functions  return  0.   Given  valid  pointer  arguments,  pthread_rwlockattr_getkind_np() always succeeds.  On error,
       pthread_rwlockattr_setkind_np() returns a non-zero error number.

ERRORS

       EINVAL pref specifies an unsupported value.

BUGS

       Setting the value read-write lock  kind	to  PTHREAD_RWLOCK_PREFER_WRITER_NP  results  in  the  same  behavior  as  setting  the  value	to
       PTHREAD_RWLOCK_PREFER_READER_NP.   As long as a reader thread holds the lock, the thread holding a write lock will be starved.  Setting the
       lock kind to PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP allows writers to run, but, as the name implies a  writer  may  not  lock  recur-
       sively.

VERSIONS

       The pthread_rwlockattr_getkind_np() and pthread_rwlockattr_setkind_np() functions first appeared in glibc 2.1.

CONFORMING TO

       These functions are non-standard GNU extensions; hence the suffix "_np" (non-portable) in the names.

SEE ALSO

       pthreads(7)

Linux Programmer's Manual					    2014-10-15					  PTHREAD_RWLOCKATTR_SETKIND_NP(3)

Check Out this Related Man Page

pthread_rwlock_wrlock(3C)												 pthread_rwlock_wrlock(3C)

NAME

       pthread_rwlock_wrlock, pthread_rwlock_trywrlock - lock or attempt to lock read-write lock object for writing

SYNOPSIS

       cc -mt [ flag... ] file... -lpthread [ library... ]
       #include <pthread.h>

       int pthread_rwlock_wrlock(pthread_rwlock_t *rwlock);

       int pthread_rwlock_trywrlock(pthread_rwlock_t *rwlock);

       The  pthread_rwlock_wrlock()  function  applies	a  write lock to the read-write lock referenced by rwlock. The calling thread acquires the
       write lock if no other thread (reader or writer) holds the read-write lock rwlock. Otherwise, the thread blocks until it  can  acquire  the
       lock.

       The  pthread_rwlock_trywrlock()	function applies a write lock like the pthread_rwlock_wrlock() function, with the exception that the func-
       tion fails if any thread currently holds rwlock (for reading or writing).

       Writers are favored over readers of the same priority to avoid writer starvation. See pthread_rwlock_rdlock(3C).

       Results are undefined if any of these functions are called with an uninitialized read-write lock.

       If a signal is delivered to a thread waiting for a read-write lock for writing, upon return from the  signal  handler  the  thread  resumes
       waiting for the read-write lock for writing as if it was not interrupted.

       If successful, the pthread_rwlock_wrlock() function returns 0. Otherwise, an error number is returned to indicate the error.

       The  pthread_rwlock_trywrlock()	function returns 0 if the lock for writing on the read-write lock object referenced by rwlock is acquired.
       Otherwise an error number is returned to indicate the error.

       The pthread_rwlock_wrlock() function will fail if:

       EDEADLK	       The current thread already owns the read-write lock for writing or reading.

       The pthread_rwlock_trywrlock() function will fail if:

       EBUSY	       The read-write lock could not be acquired for writing because it was already locked for reading or writing.

       See  attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard			   |
       +-----------------------------+-----------------------------+
       |MT-Level		     |MT-Safe			   |
       +-----------------------------+-----------------------------+

       pthread_rwlock_init(3C), pthread_rwlock_unlock(3C), pthread_rwlockattr_init(3C), pthread_rwlock_rdlock(3C), attributes(5), standards(5)

								    23 Mar 2005 					 pthread_rwlock_wrlock(3C)

Linux and UNIX Man Pages

pthread_rwlockattr_getkind_np(3) [linux man page]

Check Out this Related Man Page