resctrl_find...anest_closid(9)

💖 resctrl_find_cleanest_closid(9) 💖

okay bestie, welcome to the Kernel API Manual (section 9, we're fancy here) — this is the whole page about resctrl_find_cleanest_closid, and it's honestly kinda iconic ✨

---

🌸 NAME 🌸

resctrl_find_cleanest_closid — find a CLOSID where all the associated RMID are clean, or the CLOSID that has the most clean RMID 💅

---

🎀 SYNOPSIS 🎀

int resctrl_find_cleanest_closid (void );

---

🦋 ARGUMENTS 🦋

• void — no arguments, literally none, it takes nothing, periodt 🫶

---

✨ DESCRIPTION ✨

so here's the tea 🍓 — MPAM's equivalent of RMID is per-CLOSID, which means a freshly allocated CLOSID might not be able to allocate clean RMID. not me getting stressed about it 😭 To avoid that whole situation, the allocator will choose the CLOSID with the most clean RMID. main character allocation energy, no cap 👑

When the CLOSID and RMID are independent numbers, the first free CLOSID will be returned. slay 💅

---

🔥 RETURN 🔥

• Free CLOSID on success 🎉
• < 0 on failure 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/resctrl/monitor.c struct rmid_entry(9), cqm_setup_limbo_handler(9), mbm_setup_overflow_handler(9), struct mbm_transaction(9), resctrl_l3_mon_resource_init(9) — go read those too, iykyk 📚

---

and that's the whole vibe, bestie 💜 this lil page lives in ./fs/resctrl, dated October 2026, and it's literally called resctrl_find...anest_closid(9) in the header/footer because the name got cutely truncated — iconic behavior fr fr 😌✨