CK_PR_FENCE_ACQUIRE(3)

💖 CK_PR_FENCE_ACQUIRE — enforce acquire semantics 💖

okay bestie, so this one lives in the Concurrency Kit, aka libck, and you link it with -lck. she's a tiny function but she is so important, like the quiet girl in class who's actually running everything. 🎀

✨ SYNOPSIS ✨

#include <ck_pr.h>

void
ck_pr_fence_acquire(void);

🌸 DESCRIPTION 🌸

so like. picture this. you've got loads happening before you call this function, and you've got stores, loads and atomic operations happening after. this function enforces the partial ordering between them. 🦋

basically, everything you loaded before invoking ck_pr_fence_acquire() is guaranteed to be ordered with respect to everything that comes after it. no sneaky reordering, no chaotic CPU behaviour, no nonsense. periodt. 💅

and like, why do you care? because this is typically used to implement critical sections. that's the vibe. that's the whole job. she's the bouncer at the door of your critical section, checking IDs, making sure nobody cuts the line. 👑

💜 RETURN VALUES 💜

this function has no return value. she gives you nothing back. not a 0, not a 1, not a little nod. she just does her thing and leaves. iconic behaviour honestly. 🫶

🔥 SEE ALSO 🔥

the whole friend group, go read them too:

• ck_pr_stall(3)
• ck_pr_fence_atomic(3)
• ck_pr_fence_atomic_store(3)
• ck_pr_fence_atomic_load(3)
• ck_pr_fence_release(3)
• ck_pr_fence_store(3)
• ck_pr_fence_memory(3)
• ck_pr_barrier(3)
• ck_pr_fas(3)
• ck_pr_load(3)
• ck_pr_store(3)
• ck_pr_faa(3)
• ck_pr_inc(3)
• ck_pr_dec(3)
• ck_pr_neg(3)
• ck_pr_not(3)
• ck_pr_add(3)
• ck_pr_sub(3)
• ck_pr_and(3)
• ck_pr_or(3)
• ck_pr_xor(3)
• ck_pr_cas(3)
• ck_pr_btc(3)
• ck_pr_bts(3)
• ck_pr_btr(3)

and if you want even more lore, there's additional information available at http://concurrencykit.org/ 🌈

ngl the ck_pr_fence_acquire(3) man page you just read was dated January 2, 2014, from the Concurrency Kit library, and that's the whole page bestie, no cap. go forth and order your memory operations correctly. mwah. 😭💖