raw_read_seqcount(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… raw_read_seqcount(9) β€” straight outta the Kernel API Manual πŸŽ€

okay bestie, so this one's from the Kernel API Manual and it's lowkey one of the building blocks of the whole seqlock situation. let's get into it ✨


🌸 NAME 🌸

raw_read_seqcount β€” read the raw seqcount_t counter value. that's it. that's the vibe check. πŸ’–


✨ SYNOPSIS ✨

raw_read_seqcount (s );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • s β€” pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants. yes, any of them, the whole little family is welcome here 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so raw_read_seqcount opens a read critical section of the given seqcount_t, and here's the tea: it does it without any lockdep checking, and without checking or masking the sequence counter LSB. like, none of that. zero. not its job. πŸ’€

your calling code is the one responsible for handling that LSB situation β€” that's on you, bestie, not on this function πŸŽ€

⭐ RETURN ⭐

the count, which you then pass on to read_seqcount_retry. it's giving relay-baton energy, iykyk πŸƒβ€β™€οΈπŸ’¨


🌈 SEE ALSO 🌈

the whole friends group chat, no one left out πŸ’œ β€” plus the kernel file ./include/linux/seqlock.h:


that's the whole page, no skips, no crumbs left behind πŸ’…

this little cutie lives in ./include/linux and the version stamp says October 2026 β€” and the page signs itself off as raw_read_seqcount(9), which, iconic. mwah, go read your seqcounts responsibly πŸ§šβ€β™€οΈπŸ’œβœ¨

πŸ“¦ where this page comes from