cpumask_weighted_or(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cpumask_weighted_or(9) — from the Kernel API Manual, bestie

Okay so picture this: you're deep in ./include/linux, vibing with your cpumasks, and you need to OR two of them together and know how many bits ended up set. That's this function. It's giving "two birds, one stone" energy. 🪄✨

✨ NAME ✨

cpumask_weighted_or — literally does *dstp = *src1p | *src2p and then hands you back the weight of the result. Yes bestie, it does the OR and counts the bits. Multitasking icon. 👑

🎀 SYNOPSIS 🎀

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

Three struct cpumask * pointers walk into a function. No cap, that's the whole signature. 🫶

🌸 ARGUMENTS 🌸

  • dstp — the cpumask result. This is where the magic lands, so it's giving main character energy. Where your OR'd answer gets written. 💖
  • src1p — the first input. Input number one, doing its part. 🌼
  • src2p — the second input. Input number two, equally valid, equally needed. 🌷

⭐ RETURN ⭐

The number of bits set in the resulting cpumask dstp. So like, you get the count directly — no extra cpumask_weight(9) call needed. Efficient queen behavior. 🔥

Ngl, the return value is the weight of dstp, i.e. the result — not the inputs. Read it twice if you must, bestie, I believe in you. 💀

🦋 SEE ALSO 🦋

Everything else living in the kernel file ./include/linux/cpumask.h — the whole friend group, fr fr:

Like I said. The whole squad. Go say hi. 👋💜

That's the whole page, bestie — no crumbs left behind. 💅

Sign-off time: this little masterpiece lives at ./include/linux and it's stamped October 2026, so go forth and OR your cpumasks with confidence. 🎀🦋✨

📦 where this page comes from