cpumask_any_and_distribute(9)

💅 cpumask_any_and_distribute(9) ✨

okay so bestie, welcome to the Kernel API Manual — pull up a chair, we're talking about cpumask_any_and_distribute, and honestly? she's giving "quiet utility, loud personality." 🎀

---

✨ SYNOPSIS ✨

unsigned int cpumask_any_and_distribute (const struct cpumask *src1p ,
   const struct cpumask *src2p );

like, she takes two cpumasks and hands you back an unsigned int. that's it. that's the whole vibe. 🦋

---

🌸 ARGUMENTS 🌸

• src1p — your first cpumask, here for the intersection moment 💖
• src2p — your second cpumask, also here for the intersection moment 💖

(it takes two to tango, babes. both of them are "for intersection." no cap.)

---

👑 DESCRIPTION 👑

so here's the tea ☕ — if you keep calling this thing over and over with the same srcp1 and srcp2, the calls get distributed within their intersection. like, it rotates through the overlap so everybody gets a turn. main character energy for your CPUs, fr fr. 🌈

not me explaining set intersection like it's a group chat where only the people in both group chats get the invite 💀

---

⭐ RETURN ⭐

she returns >= nr_cpu_ids if the intersection is empty 😭 — which is the kernel-y way of saying "girl, there was literally nobody in common, so here's a number that says so."

lowkey important: if the intersection's empty, that's what you get back. don't go treating it like a real CPU id, iykyk 🫶

---

🦋 SEE ALSO 🦋

all the siblings and cousins of this function, gathered for your reading pleasure ✨:

• Kernel file ./lib/cpumask.c
• alloc_cpumask_var_node(9)
• alloc_bootmem_cpumask_var(9)
• free_cpumask_var(9)
• free_bootmem_cpumask_var(9)
• cpumask_local_spread(9)
• cpumask_any_distribute(9)

---

and that's the whole page, bestie — no crumbs left behind, every flag and fact intact, we ate and left absolutely no notes 💅

signing off from ./lib, dated October 2026, in the one and only cpumask_any_and_distribute(9) era 🎀✨🫶