SMR_PTR_GET(9)

💖 SMR_PTR_GET(9) — safe memory reclamation pointer API 💖

okay bestie, this is the SMR_PTR_GET(9) page from the Kernel Developer's Manual, and it’s giving safe memory reclamation pointer API realness. no cap, we’re about to get into the pointer macros. 💅

✨ NAME ✨

SMR_PTR_GET, SMR_PTR_GET_LOCKED, SMR_PTR_SET_LOCKED — safe memory reclamation pointer API. three macros, one cute lil family. 🫶

🌸 SYNOPSIS 🌸

TYPE
SMR_PTR_GET(TYPE *pptr);

TYPE
SMR_PTR_GET_LOCKED(TYPE *pptr);

void
SMR_PTR_SET_LOCKED(TYPE *pptr, TYPE v);

🦋 DESCRIPTION 🦋

The SMR_PTR macros are used for accessing SMR-protected pointers. that’s the whole assignment, and they ate. 💅

• SMR_PTR_GET() — reads the pointer referenced by pptr for dereferencing inside SMR read-side critical section. read-side bestie behavior, literally.
• SMR_PTR_GET_LOCKED() — reads the pointer referenced by pptr for dereferencing inside writer context. writer-context energy only. 👑
• SMR_PTR_SET_LOCKED() — writes value v to the pointer referenced by pptr. The operation issues a write-write memory barrier with membar_producer(9) before the pointer write. barrier first, then the write, periodt. 🔥

🎀 CONTEXT 🎀

SMR_PTR_GET(), SMR_PTR_GET_LOCKED() and SMR_PTR_SET_LOCKED() can be called during autoconf, from process context, or from interrupt context. yes, all three, no cap.

• SMR_PTR_GET() can be used from SMR read-side critical section.
• SMR_PTR_GET_LOCKED() and SMR_PTR_SET_LOCKED() can be used from writer context.

🌈 SEE ALSO 🌈

• membar_producer(9)
• SMR_LIST_INIT(9)
• smr_read_enter(9)

go read these next, bestie, iykyk. 💜

⭐ HISTORY ⭐

The SMR_PTR macros first appeared in OpenBSD 6.5. iconic origin story, fr fr. 🎀

---

okay that’s the page! 💖 this one is from Debian, dated July 5, 2019, for SMR_PTR_GET(9) — mwah, bestie. 💋✨