cpumask_or(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cpumask_or(9) β€” the Kernel API Manual, but make it make sense ✨

okay so bestie, welcome to the group chat 🫢 this one lives in the Kernel API Manual and it is genuinely one of the cutest little helpers in ./include/linux/cpumask.h β€” it's giving "bitwise OR but make it CPU masks" and honestly? obsessed. πŸ’–


✨ NAME ✨

cpumask_or β€” the whole entire vibe is literally this:

*dstp = *src1p | *src2p

no cap, that's it, that's the function. πŸ’…


🌸 SYNOPSIS 🌸

void cpumask_or (struct cpumask *dstp , const struct cpumask *src1p ,
       const struct cpumask *src2p );

it returns void bestie, so don't go looking for a return value, it's not coming πŸ”₯ the result goes into *dstp and that's the whole plot.


πŸŽ€ ARGUMENTS πŸŽ€

  • dstp β€” the cpumask result πŸ’« this is where the answer lands, she's the main character of this operation, the output slot, the one who gets written to. periodt.
  • src1p β€” the first input 🌸 one half of the OR, read-only, const, she is not being modified today.
  • src2p β€” the second input πŸ¦‹ the other half of the OR, also const, also just here to be read and combined. iconic behaviour honestly.

so like… dstp gets src1p | src2p and everyone else stays exactly as they were. no drama, no side effects on the sources, we love a clean bitwise moment ✨


πŸ’œ SEE ALSO πŸ’œ

literally the entire cpumask cinematic universe, iykyk πŸ‘‘

like i said. the whole universe. go read them. slay. πŸ”₯


ngl if you only remember one thing: dstp gets the OR of src1p and src2p, nothing more, nothing less. no cap. πŸ’–

okay bye bestie, this page came from ./include/linux and it's dated October 2026, so yeah, freshly stamped and ready for you πŸŽ€πŸ’…βœ¨

πŸ“¦ where this page comes from