STRUCT RMID_ENTRY(9)

💖 struct rmid_entry(9) 💖

okay so bestie, this is from the Kernel API Manual — yes, that's the manual name — and this page is all about struct rmid_entry. It's giving dirty tracking for all RMID, and honestly? It ate. 🫶✨

✨ NAME ✨

struct rmid_entry — dirty tracking for all RMID. periodt. 💅

🦋 SYNOPSIS 🦋

       struct rmid_entry {
           u32 closid;
           u32 rmid;
           int busy;
           struct list_head                list;
        };

🫶 Members 🫶

• closid — the CLOSID for this entry. That's literally its whole job. 🎀
• rmid — the RMID for this entry. iconic.
• busy — the number of domains with cached data using this RMID. So when it's busy, it's busy busy. 😭
• list — member of the rmid_free_lru list when busy == 0. Noted, bestie. 🫡

💅 Description 💅

Depending on the architecture, the correct monitor is accessed using both closid and rmid, or rmid only. So it's arch-dependent vibes — check what your architecture is on. 👀✨

🚨 IMPORTANT: Take the rdtgroup_mutex when accessing. Do not skip this. It's literally in the manual, no cap. 🔒

🌈 SEE ALSO 🌈

go read these next, bestie:

• Kernel file ./fs/resctrl/monitor.c
• resctrl_find_cleanest_closid(9)
• cqm_setup_limbo_handler(9)
• mbm_setup_overflow_handler(9)
• struct mbm_transaction(9)
• resctrl_l3_mon_resource_init(9)

mwah 💋 this page came from ./fs/resctrl, dated October 2026, and it's struct rmid_entry(9). periodt. 🎀🦋