resctrl_arch_reset_cntr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… resctrl_arch_reset_cntr(9) β€” the Kernel API Manual page, but make it make sense

okay bestie so this is a page from the Kernel API Manual and it's all about resctrl_arch_reset_cntr β€” literally the lil function that wipes the private state hanging off a counter ID. it's short, it's sweet, and yes we're gonna read the whole thing together 🫢


✨ NAME ✨

resctrl_arch_reset_cntr β€” reset any private state associated with a counter ID. that's it, that's the whole personality πŸŽ€


🌸 SYNOPSIS 🌸

void resctrl_arch_reset_cntr (struct rdt_resource *r , struct
rdt_l3_mon_domain *d , u32 closid , u32 rmid , int cntr_id , enum
resctrl_event_id eventid );

like, look at her. six arguments, returns nothing (void), absolute main character energy πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • r β€” the domain's resource. your resource, your rules πŸ’–
  • d β€” the counter ID's domain. every counter's gotta live somewhere, and this is where 🏠
  • closid β€” the CLOSID that matches the RMID. they're a matching set, iykyk ✨
  • rmid β€” the RMID that cntr_id is assigned to. the one and only πŸ”₯
  • cntr_id β€” the counter you're actually resetting. the star of the show ⭐
  • eventid β€” the MBM event that cntr_id is assigned to. context is everything, fr fr πŸ’œ

🧚 DESCRIPTION 🧚

so what does she do? she resets the private state associated with a counter ID. and the big flex:

this can be called from any CPU. no pinning, no stressing, no "wait which core am I on" panic. she's chill like that 😌

πŸ‘‘ SEE ALSO πŸ‘‘

okay this is the part where the page name-drops literally everyone in the friend group. and when I say everyone, I mean everyone β€” no cap, all of these:

like I said. the whole group chat 🌈


k bye bestie, go reset some counters πŸ’…βœ¨

this page lives over in ./include/linux, it's dated October 2026, and it's brought to you by the one and only resctrl_arch_reset_cntr(9) β€” mwah, love u, see u in the man pages πŸ“πŸŽ€

πŸ“¦ where this page comes from