cpu_latency_qos_add_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 cpu_latency_qos_add_request(9) 🌸

okay bestie, welcome to the Kernel API Manual page for cpu_latency_qos_add_request(9) β€” yes that's a whole mouthful and yes you're gonna slay it πŸ’…


✨ NAME ✨

cpu_latency_qos_add_request β€” adds a brand new CPU latency QoS request, no cap πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void cpu_latency_qos_add_request (struct pm_qos_request *req , s32 value );

like, that's the whole thing. it's giving "small but mighty" energy fr fr ✨


πŸ’– ARGUMENTS πŸ’–

  • req β€” a pointer to a handle you already allocated ahead of time (preallocated, bestie, you bring the memory) 🫢
  • value β€” the constraint value you're requesting. that's the number, the vibe, the whole point 🌈

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• β€” you take that value and use it to initialize the request handle that req points at. then the function inserts that handle as a new entry into the CPU latency QoS list, and recomputes the effective QoS constraint for that whole list. iconic behavior, honestly πŸ”₯

and like β€” callers need to save the handle for later. that handle is your main character, because you'll need it again when you want to update or remove the QoS request it represents. don't lose it. literally don't πŸ™ˆ


🧚 SEE ALSO 🧚

kernel file ./kernel/power/qos.c and all these besties:


πŸ’€ one (1) function, seventeen (17) SEE ALSO entries. the manpage said "go read the whole kernel" and honestly? respect.

and that's the page!! this one lives under ./kernel/power, dropped October 2026 β€” go forth and request your QoS, queen πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from