STRUCT RDT_RESOURCE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct rdt_resource β€” the attributes of a resctrl resource, bestie. That's it, that's the whole vibe ✨

(also hi, this is a page from the Kernel API Manual, section 9 β€” keep that in mind, it's a kernel doc thing 🫢)


✨ SYNOPSIS ✨

okay so here's the literal struct, no cap, copy it exactly:

struct rdt_resource {
    enum resctrl_res_level  rid;
    bool alloc_capable;
    bool mon_capable;
    enum resctrl_scope      ctrl_scope;
    enum resctrl_scope      mon_scope;
    struct resctrl_cache    cache;
    struct resctrl_membw    membw;
    struct resctrl_mon      mon;
    struct list_head        ctrl_domains;
    struct list_head        mon_domains;
    char *name;
    enum resctrl_schema_fmt schema_fmt;
    bool cdp_capable;
 };

like. she's giving "one struct to describe an entire resource" and honestly? iconic 🌸


πŸŽ€ MEMBERS πŸŽ€

every single field, one by one, let's go πŸ”₯

  • rid β€” the index of the resource. that's her number, her ID, her whole identity πŸ’…
  • alloc_capable β€” is allocation actually available on this machine? true = yes queen, false = not today 🫢
  • mon_capable β€” is the monitor feature available on this machine? same deal, it's a yes/no vibe check πŸ‘‘
  • ctrl_scope β€” the scope of this resource for control functions. basically: how far does she reach for control stuff 🌈
  • mon_scope β€” the scope of this resource for monitor functions. same but for monitoring, iykyk πŸ¦‹
  • cache β€” cache allocation related data. all the cache lore lives here πŸ“
  • membw β€” if the component has bandwidth controls, these are their properties. no bandwidth controls? then this part's just chilling 😭
  • mon β€” monitoring related data. the vibes she's tracking πŸ“Š
  • ctrl_domains β€” the RCU list of all control domains for this resource. yes, RCU, be normal about it πŸ’€
  • mon_domains β€” the RCU list of all monitor domains for this resource. twin of the one above, also RCU 🧚
  • name β€” the name to use in the "schemata" file. literally her display name ✨
  • schema_fmt β€” which format string and parser is used for this schema. the formatting situation πŸŽ€
  • cdp_capable β€” is the CDP feature available on this resource? CDP girlies rise πŸ™ˆ

🌟 SEE ALSO 🌟

all the kernel file neighbors, listed exactly as they are, no skipping:

Kernel file ./include/linux/resctrl.h: enum resctrl_conf_type(9), struct resctrl_staged_config(9), struct rdt_domain_hdr(9), struct rdt_ctrl_domain(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 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)


and that's the whole page bestie πŸ’œ this one shipped out from ./include/linux in October 2026, filed under struct rdt_resource(9) β€” go forth and read your structs, mwah πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from