pseudo_lock_measure_cycles(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pseudo_lock_measure_cycles(9) β€” like, the whole kernel API manual vibe πŸŽ€

okay so bestie, welcome to pseudo_lock_measure_cycles(9), straight outta the Kernel API Manual ✨ grab a strawberry drink πŸ“ and let's get into it, because this one is honestly kinda iconic.


✨ NAME ✨

pseudo_lock_measure_cycles β€” trigger latency measure to pseudo-locked region πŸ¦‹

like, it literally goes and measures the latency for you. main character energy fr fr.


🌸 SYNOPSIS 🌸

int pseudo_lock_measure_cycles (struct rdtgroup *rdtgrp , int sel );

that's it, that's the whole signature, look at her go πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • rdtgrp β€” the resource group to which the pseudo-locked region belongs. like, whose region are we even measuring here, ykwim? πŸ‘‘
  • sel β€” the selector of which measurement to perform on a pseudo-locked region. yes bestie, you get to pick which measurement, so choose wisely 🫢

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea β˜• β€” the measurement of latency to access a pseudo-locked region should be done from a cpu that is associated with that pseudo-locked region. no cap, that's just how it is.

so what happens is: it determines which cpu is associated with this region, and then it starts a thread on that cpu to perform the measurement 🌈 and then it waits for that thread to complete. patient queen behavior honestly πŸ’œ


⭐ RETURN ⭐

  • 0 on success πŸŽ‰
  • <0 on failure 😭

πŸ”₯ SEE ALSO πŸ”₯

kernel file ./fs/resctrl/pseudo_lock.c plus the whole friend group:


and that's the whole page bestie, ily, go measure some cycles πŸ’€βœ¨

source: ./fs/resctrl Β· October 2026 Β· pseudo_lock_measure_cycles(9) β€” periodt. πŸ§šβ€β™€οΈπŸ’…
πŸ“¦ where this page comes from