CK_RWCOHORT_READ_UNLOCK(3)

πŸ’… CK_RWCOHORT_READ_UNLOCK(3) β€” bestie edition ✨

okay so you're holding a read lock on a cohort-based reader-writer lock and you wanna let it go?? say less, this is literally the page for you. it's CK_RWCOHORT_READ_UNLOCK(3), from the Concurrency Kit squad 🫢


🌸 NAME 🌸

CK_RWCOHORT_READ_UNLOCK β€” the call that relinquishes read-only access to a cohort-based reader-writer lock. giving "i'm done reading, u can have the vibes back" energy πŸ“šβž‘οΈπŸ”“


πŸ“š LIBRARY πŸ“š

Concurrency Kit (libck, -lck). yeah you gotta link it, no cap. -lck bestie, don't forget it πŸ’–


✨ SYNOPSIS ✨

#include <ck_cohort.h>

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

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

CK_RWCOHORT_WP_READ_UNLOCK(COHORT_NAME cohort_name, LOCK *lock,
    COHORT *cohort"void *global_context, void *local_context);
πŸ’€ not me staring at that stray " β€” yes bestie i copied it character for character because that's the rule and i do not break the rules. keep it exactly like that. periodt.

πŸ‘‘ DESCRIPTION πŸ‘‘

so like, this call will relinquish read-only permission to lock. πŸŽ€

cohort must point to a cohort whose global lock is the same as all other cohorts used with lock. that part is not optional, it's giving "the friend group has to be the same friend group" fr fr. 🌈

the global_context and local_context arguments will be passed along as the context arguments to any calls to cohort. so they're not just decorative, they get handed off, iykyk πŸ¦‹


πŸ‘€ SEE ALSO πŸ‘€

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


and that's the whole page bestie!! πŸ’–βœ¨πŸŽ€ this icon was last touched on February 24, 2013, and it lives its life as CK_RWCOHORT_READ_UNLOCK(3) in the Concurrency Kit collection. go unlock something, you ate πŸ«ΆπŸ’…

πŸ“¦ where this page comes from