unbound_effective_cpumask(9)

📦 version 7.3.1, in nixpkgs unstable

💅 unbound_effective_cpumask 💅

okay so bestie, welcome to the unbound_effective_cpumask(9) page — it's a kernel API manual situation, and honestly? it's short, it's sweet, and it ate. let's get into it ✨

🌸 NAME 🌸

unbound_effective_cpumask — the effective cpumask of an unbound workqueue, which is literally the whole point of this function 🎀

🦋 SYNOPSIS 🦋

struct cpumask * unbound_effective_cpumask (struct workqueue_struct *wq
);

like yes, that's the whole signature, she's not doing too much 💅

💖 ARGUMENTS 💖

  • wq — the workqueue of interest 🫶 that's it, that's the argument. it's the workqueue you're curious about, the main character of this call.

✨ DESCRIPTION ✨

okay so here's the tea, and it's giving internals 🍓:

wq->attrs->cpumask holds the cpumask that the user requested. that requested one gets masked with wq_unbound_cpumask to determine the effective cpumask. iykyk.

and the default pwq? she's always mapped to the pool with the current effective cpumask. no cap, that's just how it is 💀✨

ngl this one is tiny but she matters — if you're poking at workqueue cpumasks, this is the function that tells you what's actually in effect versus what somebody asked for 👑

🌈 SEE ALSO 🌈

bestie. buckle up. this list is enormous and we are NOT skipping a single one of these 🫡💖

the kernel file here is ./kernel/workqueue.c, and then we've got:

like… that's the whole workqueue extended universe right there, and we love her for it 🧚💜

🎀 sign-off 🎀

this little icon comes from ./kernel, October 2026, and she's filed under the unbound_effective_cpumask(9) name in the Kernel API Manual. slay, go read your cpumasks, periodt 👑✨

📦 where this page comes from