oom_cpuset_eligible(9)

okay bestie, welcome to oom_cpuset_eligible(9) from the Kernel API Manual — the eligibility check that’s lowkey iconic. 💅✨

🌸 NAME 🌸

• oom_cpuset_eligible — check task eligibility for kill. that’s the name, that’s the job, periodt. 💖

✨ SYNOPSIS ✨

bool oom_cpuset_eligible (struct task_struct *start , struct oom_control
*oc );

🎀 ARGUMENTS 🎀

• start — task struct of the task to consider 👀. like, the task you’re looking at, bestie.
• oc — pointer to struct oom_control 🎀. literally a pointer to that struct, no cap.

💅 DESCRIPTION 💅

okay so task eligibility is determined by these specifics: whether or not a candidate task, tsk, shares the same mempolicy nodes as current if it is bound by such a policy, and whether or not it has the same set of allowed cpuset nodes. that’s the rubric, bestie — no extra side quests. 🌈

heads up 🫶: this function is assuming oom-killer context and that 'current' has triggered the oom-killer. fr fr, that’s the assumption.

🦋 SEE ALSO 🦋

the whole squad, go read up 👑:

• Kernel file ./mm/oom_kill.c — yes, that exact path. 📂
• oom_badness(9) — iconic. 💅
• dump_tasks(9) — also iconic. 💜
• mark_oom_victim(9) — yep. 🔥
• exit_oom_victim(9) — yep. 🌸
• oom_killer_enable(9) — yep. ⭐
• oom_killer_disable(9) — yep. 🦋
• out_of_memory(9) — yep. 💖

byeee bestie 🫶💖 — this page is from the ./mm source/version, dated October 2026, and it’s oom_cpuset_eligible(9) signing off. 💅✨