P99_ACCOUNT p99_cm p99_cm_destroy P99_CM_EXCLUDE p99_cm_init P99_CM_INITIALIZER p99_cm_lock p99_cm_trylock p99_cm_unlock p99_cm_wait p99_count_destroy p99_count_init p99_count_init P99_COUNT_INITIALIZER p99_count_value p99_count_wait p99_event p99_event_destroy p99_event_init p99_event_next p99_event_signal p99_futex_add p99_futex_destroy p99_futex_exchange p99_futex_init p99_futex_load p99_futex_wait p99_futex_wakeup p99_iterator p99_iterator_destroy p99_iterator_init p99_iterator_next p99_iterator_signal p99_notifier_block p99_notifier_destroy p99_notifier_init P99_NOTIFIER_INITIALIZER p99_notifier_load P99_RDLOCK p99_rwl_destroy p99_rwl_haswaiters p99_rwl_init P99_RWL_INITIALIZER p99_rwl_islocked p99_rwl_rdlock p99_rwl_unlock p99_rwl_wrlock P99_WRLOCK

p99_cm typedef struct p99_cm p99_cm A simple condition-mutex data structure. This combines elements of standard mtx_t and cnd_t into one simple lock. Namely it implements three basic control interfaces p99_cm_lock, p99_cm_unlock and p99_cm_wait. There is no separate interface that would correspond to ::cnd_signal or ::cnd_broadcast, because the wake up functionality is already integrated into p99_cm_unlock. This is meant to be simple or even simplistic: There are no variants of this that would correspond to recursive or timed locks. None of the blocking states can be canceled. Ownership of the lock is not tracked. If a thread calls p99_cm_unlock while another thread effectively holds the lock and relies on the fact that he is alone in a critical section, bad things can happen. If the thread that was holding the lock has exited, p99_cm_unlock can be used to unblock the condition-mutex. See also p99_cm_lock p99_cm_unlock p99_cm_trylock p99_cm_wait P99_CM_EXCLUDE Definition at line 63 of file p99_cm.h.