bfq_updated_next_req(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bfq_updated_next_req(9) β€” Kernel API Manual πŸ’…

πŸ’– NAME πŸ’–

bfq_updated_next_req β€” update the queue after a new next_rq selection. ✨

✨ SYNOPSIS ✨

void bfq_updated_next_req (struct bfq_data *bfqd , struct bfq_queue
*bfqq );

okay so it’s a void function, bestie β€” no return value to obsess over, just queue-update main character energy πŸ’«

πŸŽ€ ARGUMENTS πŸŽ€

  • bfqd β€” the device data the queue belongs to. πŸ–₯οΈπŸ’–
  • bfqq β€” the queue to update. πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here’s the tea β˜•: if the first request of a queue changes, we make sure that the queue has enough budget to serve at least its first request β€” specifically if the request has grown. πŸ“ˆβœ¨

We do this because if the queue has not enough budget for its first request, it has to go through two dispatch rounds to actually get it dispatched. 😭 no cap, that’s the whole reason β€” the queue needs its budget moment so its first request can actually get dispatched without the whole two-round situation. πŸ’…

🌈 SEE ALSO 🌈


okay bye bestie 🫢 this page lives in ./block, dated October 2026, and the footer cutie is literally bfq_updated_next_req(9) again β€” iconic, no notes πŸ’…βœ¨

πŸ“¦ where this page comes from