atomic64_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… atomic64_read(9)

okay so this is a page from the Kernel API Manual β€” yes, the Kernel API Manual, we're in the big leagues now bestie πŸŽ€ β€” and it's about atomic64_read(9). Sit down, hydrate, let's go. πŸ’–


✨ NAME ✨

atomic64_read β€” an atomic load with relaxed ordering. That's it. That's the whole vibe. ⭐


🌸 SYNOPSIS 🌸

s64 atomic64_read (const atomic64_t *v );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • v β€” pointer to atomic64_t. a lil pointer, pointing at your atomic sixty-four-y thing 🫢

πŸ’… DESCRIPTION πŸ’…

okay so lowkey the whole job: it atomically loads the value of v with relaxed ordering. like, the load happens as one indivisible unit, no sneaky half-reads, but relaxed ordering means it's not out here making promises about ordering with other operations. it's chill. it's relaxed. it's giving "i'm just here to read a value" 😌✨

⚠️ not me telling you this but β€” it's unsafe to use in noinstr code. use raw_atomic64_read there instead. fr fr, don't fight the manpage on this one. πŸ’€

πŸ‘‘ RETURN πŸ‘‘

The value loaded from v. that's it, that's the tea πŸ“


🌈 SEE ALSO 🌈

the manpage points you at the kernel file ./include/linux/atomic/atomic-instrumented.h, and then it absolutely dumps the entire extended family on you. and i mean the whole family. buckle up πŸ’€πŸ”₯

the 32-bit atomic_* icons β€” a thread 🧡

the atomic64_* girlies (this one's family 🫢)

the atomic_long_* crew (they said "long" and meant it 😭)

like… that's the whole friend group. every single one of them. no cap. πŸ”₯πŸ‘‘


and that's the page bestie πŸ’œ huge slay, go read your atomics responsibly. this one came out of the source file ./include/linux/atomic, dated October 2026, and it's filed under atomic64_read(9) β€” mwah, bye βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from