pseudo_lock_region_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so welcome to the pseudo_lock_region_init(9) page from the Kernel API Manual, bestie πŸ’– this one is literally about initializing pseudo-lock region information, and it's giving very specific setup energy.


πŸ¦‹ SYNOPSIS πŸ¦‹

int pseudo_lock_region_init (struct pseudo_lock_region *plr );

πŸ’… ARGUMENTS πŸ’…

  • plr β€” the pseudo-lock region 🫢 this is the little region struct we're setting up.

✨ DESCRIPTION ✨

so picture this: this function is called after the user already provided a schemata to be pseudo-locked. On entry, struct pseudo_lock_region is already initialized with the resource, domain, and capacity bitmask. From that data, this function deduces the info required for pseudo-locking and initializes struct pseudo_lock_region further. highkey important stuff 😌

the information it works out includes:

  • size in bytes of the region to be pseudo-locked πŸ“
  • cache line size, so we know the stride with which data needs to be accessed to be pseudo-locked 🧚
  • a CPU associated with the cache instance on which the pseudo-locking flow can be executed πŸ‘‘

πŸ”₯ RETURN πŸ”₯

0 on success, <0 on failure. A descriptive error will be written to the last_cmd_status buffer 😭 no cap, that's where the tea gets spilled.


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./fs/resctrl/pseudo_lock.c β€” and the whole SEE ALSO squad is:


made with πŸ’– from the source/version ./fs/resctrl, dated October 2026 β€” that's the cute little sign-off, bestie, bye! πŸŽ€

πŸ“¦ where this page comes from