pseudo_lock_free(9)
π
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 yourstruct 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 π:
pseudo_lock_minor_get(9)pseudo_lock_minor_release(9)region_find_by_minor(9)struct pseudo_lock_pm_req(9)pseudo_lock_cstates_constrain(9)pseudo_lock_region_clear(9)pseudo_lock_region_init(9)pseudo_lock_init(9)pseudo_lock_region_alloc(9)rdtgroup_monitor_in_progress(9)rdtgroup_locksetup_user_restrict(9)rdtgroup_locksetup_user_restore(9)rdtgroup_locksetup_enter(9)rdtgroup_locksetup_exit(9)rdtgroup_cbm_overlaps_pseudo_locked(9)rdtgroup_pseudo_locked_in_hierarchy(9)pseudo_lock_measure_cycles(9)rdtgroup_pseudo_lock_create(9)rdtgroup_pseudo_lock_remove(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms