← Manual Pages
CK_EPOCH_BARRIER(3) BSD Library Functions Manual CK_EPOCH_BARRIER(3)
ck_epoch_barrier -- block until a grace period and all callbacks have
Concurrency Kit (libck, -lck)
The ck_epoch_barrier(3) function will block the caller until a grace
period has been detected, according to the semantics of epoch reclama-
tion. Any objects requiring safe memory reclamation which are logically
deleted are safe for physical deletion following a call to
ck_epoch_barrier(3). This function will also dispatch all callbacks asso-
ciated with epoch that were previously scheduled via ck_epoch_call(3).
* epoch was previously initialized with ck_epoch_init.
* stack was previously initialized with ck_stack_init.
record = malloc(sizeof *record);
* We are using an epoch section here to guarantee no
* nodes in the stack are deleted while we are dereferencing
* them. This is needed here because there are multiple writers.
* If there was only one thread popping from the this stack,
* then there is no need to ck_epoch_begin/ck_epoch_end.
/* Logically delete an object. */
s = ck_stack_pop_upmc(stack);
* Wait until no threads could possibly have a reference to the
* object we just popped (assume all threads are simply executing
/* It is now safe to physically delete the object. */
This function has no return value.
Behavior is undefined if the object pointed to by epoch is not a valid
epoch object. The object pointed to by record must have been previously
registered via ck_epoch_register(3).
ck_epoch_init(3), ck_epoch_register(3), ck_epoch_unregister(3),
ck_epoch_recycle(3), ck_epoch_poll(3), ck_epoch_synchronize(3),
ck_epoch_reclaim(3), ck_epoch_call(3), ck_epoch_begin(3), ck_epoch_end(3)
Additional information available at http://concurrencykit.org/
September 2, 2012