raw_atomic_l...read_acquire(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 raw_atomic_long_read_acquire β€” NAME πŸ’…

okay bestie so raw_atomic_long_read_acquire is literally an atomic load with acquire ordering ✨ and she's from the Kernel API Manual (section 9, kernel devs only, iykyk πŸŽ€). that's the whole name. no notes. periodt.


✨ SYNOPSIS ✨

long raw_atomic_long_read_acquire (const atomic_long_t *v );

like, she takes one pointer and hands you back a long. that's it. that's the whole girl 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • v β€” pointer to atomic_long_t. yes that's the entire description. she's a pointer to an atomic_long_t. iconic, minimal, no cap πŸ”₯

πŸ‘‘ DESCRIPTION πŸ‘‘

so what she does is atomically load the value of v with acquire ordering πŸ’– like, one clean read, no torn values, and the acquire ordering means everything is ordered properly around it. slay.

she is safe to use in noinstr code β€” that's the whole reason she exists as a raw_ version, bestie 🌟

🫢 but like... prefer atomic_long_read_acquire elsewhere. raw_atomic_long_read_acquire is the noinstr-safe one; the regular atomic_long_read_acquire is the one you should be reaching for in normal code. the way that's literally in the manpage, so don't come for me πŸ’€

πŸ’œ RETURN πŸ’œ

the value loaded from v. she read it, she gives it to you, done. no errors, no surprises, main character energy only πŸ‘‘βœ¨


🌈 SEE ALSO 🌈

okay this is the part where she introduces you to her entire extended family 😭 β€” like genuinely all of them, so buckle up πŸ“. and the kernel file that houses this whole dynasty:

like... 84 cousins. she's got a big family and she loves them all πŸ’œβœ¨


bye bestie!! πŸ’– this page lives at ./include/linux/atomic, and it was stamped October 2026 β€” so go forth, load atomically, and stay noinstr-safe πŸ§šβ€β™€οΈπŸŽ€β­

πŸ“¦ where this page comes from