dev_pm_qos_...cy_tolerance(9)
π dev_pm_qos_...cy_tolerance(9) π
okay so bestie, you're reading a page from the Kernel API Manual (yes, the Kernel API Manual, we're in the big leagues now π) and the star of the show is literally the function dev_pm_qos_get_user_latency_tolerance. Say it three times fast, iykyk π
β¨ NAME β¨
dev_pm_qos_get_user_latency_tolerance β get the user space latency tolerance, bestie. That's the whole vibe. π«Ά
πΈ SYNOPSIS πΈ
s32 dev_pm_qos_get_user_latency_tolerance (struct device *dev );
Like, that's it. One argument. We love a low-maintenance icon π
π ARGUMENTS π
devβ the device you want the user space latency tolerance for. That's the one. That's the device. Point at it and this function does its thing β¨
π¦ SEE ALSO π¦
so there's a whole friend group here and honestly they're all iconic in their own way π The kernel file we're living in is ./drivers/base/power/qos.c, and here's the full squad, no cap:
__dev_pm_qos_flags(9)dev_pm_qos_flags(9)__dev_pm_qos_resume_latency(9)dev_pm_qos_read_value(9)apply_constraint(9)dev_pm_qos_constraints_destroy(9)dev_pm_qos_add_request(9)__dev_pm_qos_update_request(9)dev_pm_qos_update_request(9)dev_pm_qos_remove_request(9)dev_pm_qos_add_notifier(9)dev_pm_qos_remove_notifier(9)dev_pm_qos_add_ancestor_request(9)dev_pm_qos_expose_latency_limit(9)dev_pm_qos_hide_latency_limit(9)dev_pm_qos_expose_flags(9)dev_pm_qos_hide_flags(9)dev_pm_qos_update_flags(9)dev_pm_qos_update_user_latency_tolerance(9)dev_pm_qos_expose_latency_tolerance(9)dev_pm_qos_hide_latency_tolerance(9)
like, go read them too?? they're all right there in ./drivers/base/power, being useful and slaying ππ₯
ngl bestie, this page came straight out of ./drivers/base/power and it's dated October 2026, so jot that down ποΈβ¨
and that's the whole page, mwah π β go get that latency tolerance, main character π§π
π¦ 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