STRUCT RDT_CTRL_DOMAIN(9)
π 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β whenmba_scis enabled, this holds the array of user-specified control values formba_scin MBps, indexed byclosid. so yeah, it's an array, it's user-specified, it's in MBps, andclosidis doing the indexing π
π¦ SEE ALSO π¦
literally go read these next, bestie:
- Kernel file
./include/linux/resctrl.h enum resctrl_conf_type(9)struct resctrl_staged_config(9)struct rdt_domain_hdr(9)struct mbm_cntr_cfg(9)struct rdt_l3_mon_domain(9)struct resctrl_cache(9)enum membw_throttle_mode(9)struct resctrl_membw(9)enum resctrl_schema_fmt(9)struct resctrl_mon(9)struct rdt_resource(9)struct resctrl_schema(9)resctrl_arch_sync_cpu_closid_rmid(9)resctrl_get_default_ctrl(9)resctrl_arch_mon_event_config_write(9)resctrl_arch_mon_event_config_read(9)resctrl_arch_mbm_cntr_assign_enabled(9)resctrl_arch_mbm_cntr_assign_set(9)resctrl_arch_rmid_read(9)resctrl_arch_rmid_read_context_check(9)resctrl_find_domain(9)resctrl_arch_reset_rmid(9)resctrl_arch_reset_rmid_all(9)resctrl_arch_reset_all_ctrls(9)resctrl_arch_config_cntr(9)resctrl_arch_cntr_read(9)resctrl_arch_reset_cntr(9)resctrl_arch_io_alloc_enable(9)resctrl_arch_get_io_alloc_enabled(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms