scx_cmask_fill(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scx_cmask_fill β€” from the Kernel API Manual (section 9, kernel space only, no userland shenanigans) πŸŽ€

okay bestie, sit down, hydrate, and let's talk about scx_cmask_fill ✨ this one's a little cutie from the scx_cmask family and honestly she's giving "just do one thing and do it well" energy πŸ‘‘


🌸 NAME 🌸

scx_cmask_fill β€” sets every single bit in @m's active range 🫢

Like, all of them. The whole active range. Filled. Done. Slay.


✨ SYNOPSIS ✨

void scx_cmask_fill (struct scx_cmask *m );

no return value, no drama, she just does the thing πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • m β€” the cmask to fill 🌈 (yes that's the whole argument list, she's low maintenance)

πŸ’– DESCRIPTION πŸ’–

So here's the vibe: scx_cmask_fill is the literal counterpart to scx_cmask_clear πŸ” one of them turns the bits on, one of them turns the bits off, and they're besties about it.

She sets every bit in @m's active range β€” and that's it. Anything stored past the active range? Not her business, not her problem, she leaves it as is πŸ™ˆ no cap, she will not touch it.

fr fr: "leaves storage past the active range as is" is not a bug, it's the spec. Don't come for her πŸ’€

🧚 SEE ALSO 🧚

the whole friend group πŸ’œ go say hi:


that's the whole page, bestie, you ate that πŸ“ this icon lives in ./kernel/sched/ext and the version stamp says October 2026 ⭐ manual section 9, kernel API manual, main character energy only πŸ’…βœ¨

periodt. πŸ¦‹

πŸ“¦ where this page comes from