Provided by: libck-dev_0.6.0-1.1_amd64 bug

NAME

     CK_RWCOHORT_READ_LOCK — acquire read-only permission for cohort-based reader-writer lock

LIBRARY

     Concurrency Kit (libck, -lck)

SYNOPSIS

     #include <ck_cohort.h>

     CK_RWCOHORT_NEUTRAL_READ_LOCK(COHORT_NAME cohort_name, LOCK *lock,
         COHORT *cohort"void *global_context, void *local_context);

     CK_RWCOHORT_RP_READ_LOCK(COHORT_NAME cohort_name, LOCK *lock,
         COHORT *cohort"void *global_context, void *local_context);

     CK_RWCOHORT_WP_READ_LOCK(COHORT_NAME cohort_name, LOCK *lock,
         COHORT *cohort"void *global_context, void *local_context);

DESCRIPTION

     This call will acquire read-only permission from lock.  The call will block until this
     permission has been acquired.  cohort must point to a cohort whose global lock is the same
     as all other cohorts used with lock.  The global_context and local_context arguments will be
     passed along as the context arguments to any calls to cohort.

SEE ALSO

     ck_cohort(3), CK_RWCOHORT_PROTOTYPE(3), CK_RWCOHORT_INSTANCE(3), CK_RWCOHORT_INITIALIZER(3),
     CK_RWCOHORT_INIT(3), CK_RWCOHORT_READ_UNLOCK(3), CK_RWCOHORT_WRITE_LOCK(3),
     CK_RWCOHORT_WRITE_UNLOCK(3),

     Additional information available at http://concurrencykit.org/

                                        February 24, 2013.