cpuset_mems_...d_intersects(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cpuset_mems_...d_intersects(9) 💅

okay bestie, so this page comes at you straight out of the Kernel API Manual, and the title it's filed under is literally cpuset_mems_...d_intersects(9) — yes, with the dots and everything, that's not a glitch, that's just how it's listed ✨

🌸 NAME 🌸

cpuset_mems_allowed_intersects — the little function that answers the question: does @tsk1's mems_allowed intersect @tsk2's? 🫶

✨ SYNOPSIS ✨

int cpuset_mems_allowed_intersects (const struct task_struct *tsk1 ,
       const struct task_struct *tsk2 );

like, that's the whole signature, no cap 💖

🎀 ARGUMENTS 🎀

  • tsk1 — a pointer to the task_struct of some task. just, y'know, a task. any task. one of them 👑
  • tsk2 — a pointer to the task_struct of some other task. the other one. the plus-one 🦋

💜 DESCRIPTION 💜

So the whole vibe here: return true if tsk1's mems_allowed intersects the mems_allowed of tsk2. that's it, that's the function, and honestly? iconic 🌟

Who's out here calling it? the OOM killer — yes, that one 😭 — and it uses this to figure out whether one of the tasks' memory usage might impact the memory available to the other. literally a vibe check but for node masks 🔥

🌈 SEE ALSO 🌈

the source lives in the kernel file ./kernel/cgroup/cpuset.c, and here's the whole cpuset crew, bestie — every single one of them, no skips:

ngl that's a lot of siblings, but they're all family, and family's family 💀

and that's a wrap, bestie 🎀 this page is filed under ./kernel/cgroup, dated October 2026, and it's the cpuset_mems_...d_intersects(9) entry in your Kernel API Manual — go forth and intersect those mems 💅✨🍓

📦 where this page comes from