bpf_cpumask_copy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– bpf_cpumask_copy(9) β€” from the Kernel API Manual πŸ’–

okay so bestie, picture this: you've got a cpumask, right? and you want it inside a BPF cpumask. that's literally the whole plot. this little kfunc is the copy-paste of the kernel world and honestly? she ate. πŸŽ€


✨ SYNOPSIS ✨

__bpf_kfunc void bpf_cpumask_copy (struct bpf_cpumask *dst , const
       struct cpumask *src );

no cap, that's the whole signature. two pointers, zero drama. πŸ’…


🫢 ARGUMENTS 🫢

  • dst β€” the BPF cpumask you're copying into. she's the destination, the main character, the one getting the glow-up. ✨
  • src β€” the cpumask you're copying from. the source material. iconic, but not the one being written to.

🌸 DESCRIPTION 🌸

so what does it actually do? it copies the contents of a cpumask into a BPF cpumask. that's it. that's the vibe check passed. πŸ¦‹

and here's the tea: a struct bpf_cpumask pointer may be safely passed to src. lowkey a nice little convenience, highkey worth remembering β€” you don't have to stress about that one. πŸ’œ

⚠️ note bestie: the manual gives us exactly that one line of description and nothing more, so no extra lore, no secret tricks. we report, we don't invent. periodt. 🌈

πŸ‘‘ SEE ALSO πŸ‘‘

like, the whole friend group. seriously, the entire cpumask clique shows up:

go read them all, i'll wait. πŸ“


and that's the page! shipped from ./kernel/bpf, dated October 2026, straight out of the Kernel API Manual. ty for coming to my ted talk, mwah πŸ’‹πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from