rdtgroup_mod...st_exclusive(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ rdtgroup_mod...st_exclusive(9) πŸ¦‹

okay so first things first, bestie β€” this page lives in the Kernel API Manual, and the function we're stanning today is rdtgroup_mode_test_exclusive. it's giving "small function, big feelings". let's get into it πŸ’…


✨ NAME ✨

rdtgroup_mode_test_exclusive β€” the little vibe-check that tells you whether this resource group can be exclusive or not 🫢


✨ SYNOPSIS ✨

bool rdtgroup_mode_test_exclusive (struct rdtgroup *rdtgrp );

✨ ARGUMENTS ✨

  • rdtgrp β€” the resource group, and no cap, it's identified through its closid. that's the whole personality of this parameter tbh πŸŽ€

✨ DESCRIPTION ✨

so like. an exclusive resource group means exactly what it sounds like β€” there should be no sharing of its allocated resources. none. zero. not even a little. it's main character energy, it doesn't do roommates 🌟

and at the moment this group is being considered for exclusive status, this test is what determines whether its current schemata actually supports that setting β€” by testing for overlap with all the other resource groups. literally checking if anybody else is squatting on its allocations πŸ™ˆ


✨ RETURN ✨

  • true β€” slay, the resource group can be exclusive πŸ’–
  • false β€” nope, there's overlap with allocations of other resource groups, which means this resource group cannot be exclusive 😭 that's the whole tea.

✨ SEE ALSO ✨

the kernel file is ./fs/resctrl/rdtgroup.c β€” go read it, iykyk πŸ“–βœ¨

and here's the whole friend group of related functions, all of them, none skipped, we don't do that here:


lowkey a reminder that this is all documented behavior, so don't go inventing new semantics, bestie β€” the manpage is the source of truth πŸ’€

and that's the page!! πŸŽ€ this one comes from the ./fs/resctrl crew, dated October 2026, and it's filed under rdtgroup_mod...st_exclusive(9) β€” okay bye, go read some kernel source, ily πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from