l3_mon_domain_mbm_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

l3_mon_domain_mbm_alloc(9) is living in the Kernel API Manual, and this whole page is about one very specific little allocation moment. Bestie, it’s giving β€œset aside arch private storage for the MBM counters,” no cap. πŸ’…

✨ NAME ✨

l3_mon_domain_mbm_alloc β€” allocate arch private storage for the MBM counters. That’s the whole assignment, and she ate. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

int l3_mon_domain_mbm_alloc (u32 num_rmid , struct rdt_hw_l3_mon_domain
*hw_dom );

Okay so here’s the tea, bestie: this is the exact signature. Character-for-character, periodt. πŸŽ€

πŸŽ€ ARGUMENTS πŸŽ€

  • num_rmid β€” the size of the MBM counter array. That’s the number she needs for the array, fr fr. πŸ“
  • hw_dom β€” the domain that owns the allocated arrays. She’s the main character holding the arrays. πŸ‘‘

πŸ’– RETURN πŸ’–

0 for success, or -ENOMEM. That’s it, that’s the whole mood: zero is the slay outcome, and -ENOMEM is the other possible return. 😭

🌈 SEE ALSO 🌈


This page came from the source tree at ./arch/x86/kernel/cpu/resctrl, dated October 2026, and it’s signing off with all the sparkle: stay allocated, bestie. πŸ’œπŸŽ€πŸ«Ά

πŸ“¦ where this page comes from