raw_atomic6...dnot_acquire(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ raw_atomic6...dnot_acquire(9) πŸ¦‹

okay bestie, this is the Kernel API Manual page for raw_atomic6...dnot_acquire(9) β€” yes the page name is giving β€œtruncated but iconic,” and the actual function is raw_atomic64_fetch_andnot_acquire. we’re gonna go through every crumb, no cap. πŸ’…


πŸ’– NAME πŸ’–

raw_atomic64_fetch_andnot_acquire β€” atomic bitwise AND NOT with acquire ordering. that’s the whole assignment, bestie. ✨


✨ SYNOPSIS ✨

s64 raw_atomic64_fetch_andnot_acquire (s64 i , atomic64_t *v );

🧚 ARGUMENTS 🧚

  • i β€” a s64 value. this is the value getting flipped and ANDed in, okay? 🫢
  • v β€” pointer to atomic64_t. this is the atomic thing being updated; she’s the main character of the memory-ordering moment. πŸ‘‘

πŸ’« DESCRIPTION πŸ’«

Atomically updates v to (v & ~i) with acquire ordering. periodt. she does the bitwise AND NOT atomically, and the ordering is acquire, so the synchronization girlies are seated. πŸ’–

Safe to use in noinstr code; prefer atomic64_fetch_andnot_acquire elsewhere. so yes, she’s allowed in noinstr land, but if you’re not in that special no-instrumentation zone, the regular atomic64_fetch_andnot_acquire is the recommended icon. 🌟


πŸŽ€ RETURN πŸŽ€

The original value of v. not the new value β€” the original. so you can see what v was before the AND NOT happened, iykyk. πŸ’…


🌈 SEE ALSO 🌈


made with πŸ’– from the source/version line ./include/linux/atomic, dated October 2026, for raw_atomic6...dnot_acquire(9). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from