pseudo_lock_free(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pseudo_lock_free(9) β€” like, the pseudo_lock_free page from the Kernel API Manual, bestie ✨

Okay so picture this: it's a (9) page, it lives in the Kernel API Manual, and it's literally all about freeing a pseudo-locked region. Yes queen, we're doing kernel resctrl internals today. πŸŽ€


🌸 NAME 🌸

pseudo_lock_free β€” frees a pseudo-locked region, that's the whole vibe πŸ’–


✨ SYNOPSIS ✨

void pseudo_lock_free (struct rdtgroup *rdtgrp );

That's it. That's the function. No return value, no drama, just void and a pointer. Iconic behavior honestly. πŸ¦‹


🫢 ARGUMENTS 🫢

  • rdtgrp β€” the resource group that the pseudo-locked region belonged to. Like, past tense, it's giving "we used to be together" 😭. This is your struct rdtgroup * and it's the only thing you're passing in.

πŸ’œ DESCRIPTION πŸ’œ

So here's the sitch, bestie: by the time you're calling this, the pseudo-locked region's resources have already been released β€” or honestly? They were never even created yet at this point. Either way, not your problem anymore. πŸ™ˆ

Now that we're here, the region can be freed and disassociated from the resource group. That's literally it. Cut the cord, release the region, let it go, main character exit. ✨

No cap, this is the cleanup step, so don't come in here expecting it to do the releasing for you β€” the manpage says the resources are already handled by the time you arrive. πŸ’…

🌈 RETURN 🌈

void β€” returns nothing, gives nothing, takes nothing. A true minimalist. πŸ‘‘


⭐ SEE ALSO ⭐

All the siblings and cousins and adjacent lore, live from the kernel file ./fs/resctrl/pseudo_lock.c πŸ“:


And that's the page, babes! 🧚 Run it back anytime you're in ./fs/resctrl, dated October 2026, and remember: pseudo_lock_free(9) said what it said. Bye bestie, slay your cleanup πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from