bpf_cpumask_intersects(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bpf_cpumask_intersects β€” the Kernel API Manual of "do these two cpumasks share a bit, bestie?" πŸŽ€

ok so picture this: you're in bpf_cpumask_intersects(9), the section 9 of the Kernel API Manual, and you just wanna know if two cpumasks are vibing on the same bit. That's literally it. That's the whole function. Let's get into it ✨


🌸 SYNOPSIS 🌸

__bpf_kfunc bool bpf_cpumask_intersects (const struct cpumask *src1 ,
       const struct cpumask *src2 );

that's the whole signature, no cap. two const struct cpumask * pointers walk in, a bool walks out 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • src1 β€” the first input, bestie. your opening act. the main character of the pair πŸ’…
  • src2 β€” the second input. the plus-one. the other half of the duo πŸŽ€

⭐ RETURN ⭐

  • true β€” src1 and src2 have at least one of the same bits set. they overlap. they're matching. it's giving soulmate energy πŸ”₯
  • false β€” src1 and src2 don't have any of the same bits set. zero overlap. not a single shared bit. it's giving two strangers at the same party πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

so here's the tea: struct bpf_cpumask pointers may be safely passed to src1 and src2. that's it, that's the note. safe to pass 🫢 no sketchy casts, no "are you sure", you're good.


πŸ‘‘ SEE ALSO πŸ‘‘

the lore, the family tree, the whole group chat:


ok that's the whole page, go check your bits and slay πŸ’…βœ¨

this cutie dropped from ./kernel/bpf in October 2026, and yeah, the header said bpf_cpumask_intersects(9) at the top and the footer said the same down here β€” iconic bookends, honestly πŸŽ€

πŸ“¦ where this page comes from