rdtgroup_pseudo_lock_create(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to rdtgroup_pseudo_lock_create(9) β€” the kernel API manual page for creating a pseudo-locked region. it’s giving lowkey resctrl realness, and we’re gonna read it together πŸ’–βœ¨

πŸŽ€ NAME πŸŽ€

rdtgroup_pseudo_lock_create β€” Create a pseudo-locked region 🌸

πŸ¦‹ SYNOPSIS πŸ¦‹

int rdtgroup_pseudo_lock_create (struct rdtgroup *rdtgrp );

🌈 ARGUMENTS 🌈

  • rdtgrp β€” the resource group to which the pseudo-lock region belongs. like, this is the group bestie, no cap 🫢

✨ DESCRIPTION ✨

So this function gets called when a resource group that’s chilling in pseudo-locksetup mode receives a valid schemata that should be pseudo-locked. because the resource group is in pseudo-locksetup mode, the struct pseudo_lock_region has already been allocated and initialized with the essential information. iconic setup behavior, honestly πŸ’…

small but important note: if a failure occurs, the resource group remains in the pseudo-locksetup mode with the struct pseudo_lock_region associated with it, but cleared from all information and ready for the user to re-attempt pseudo-locking by writing the schemata again. so it’s not down bad forever β€” it’s ready for a retry 😭✨

πŸ’œ RETURN πŸ’œ

  • 0 if the pseudo-locked region was successfully pseudo-locked, <0 on failure.
  • a descriptive error will be written to the last_cmd_status buffer. yes bestie, it tells you what went wrong 🩷

πŸ”₯ SEE ALSO πŸ”₯

kernel file ./fs/resctrl/pseudo_lock.c β€” and here’s the whole bestie lineup:


mwah πŸ’‹ that’s the whole page β€” source/version: ./fs/resctrl, date: October 2026, page: rdtgroup_pseudo_lock_create(9). ily, byeee πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from