STRUCT RDT_CTRL_DOMAIN(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct rdt_ctrl_domain(9) πŸ’…

okay bestie, welcome to the kernel API manual ✨ β€” this one's all about struct rdt_ctrl_domain, which is literally just a group of CPUs sharing a resctrl control resource. that's the whole vibe. a little squad of CPUs pooling their control resources together 🫢


🌸 SYNOPSIS 🌸

here's the shape of it, no cap:

struct rdt_ctrl_domain {
    struct rdt_domain_hdr           hdr;
    struct pseudo_lock_region       *plr;
    struct resctrl_staged_config    staged_config[CDP_NUM_TYPES];
    u32 *mbps_val;
 };

✨ Members ✨

so like, member by member, here's the tea πŸ“:

  • hdr β€” the common header for different domain types. every domain type shares this lil header, iykyk πŸ‘‘
  • plr β€” the pseudo-locked region (if any) that's associated with this domain. key words: if any πŸ™ˆ
  • staged_config β€” the parsed configuration that's just sitting there waiting to be applied. it's giving "outfit picked out but not worn yet" πŸ’…
  • mbps_val β€” when mba_sc is enabled, this holds the array of user-specified control values for mba_sc in MBps, indexed by closid. so yeah, it's an array, it's user-specified, it's in MBps, and closid is doing the indexing πŸ“Š

πŸ¦‹ SEE ALSO πŸ¦‹

literally go read these next, bestie:


aaaaand that's the whole page!! πŸŽ€ it lives in ./include/linux in the kernel tree, dated October 2026, and it's part of the Kernel API Manual, bestie. go forth and group your CPUs πŸŒˆβ­πŸ’œ

πŸ“¦ where this page comes from