bfq_lookup_next_entity(9)

✨ NAME ✨ — bfq_lookup_next_entity(9), from the Kernel API Manual

Okay bestie, so bfq_lookup_next_entity is literally the function that returns the first eligible entity in @sd. That's the whole assignment. 💅

🌸 SYNOPSIS 🌸

struct bfq_entity * bfq_lookup_next_entity (struct bfq_sched_data *sd ,
       bool expiration );

🎀 ARGUMENTS 🎀

• sd — the sched_data. That's the vibe, no extra lore. 💖
• expiration — true if we are on the expiration path of the in-service queue. Yes, that exact situation. 👑

🦋 DESCRIPTION 🦋

So picture this: there has been a change in the trees for sd, and we need to know what the new next entity to serve is after this change. That's exactly when this function gets invoked. It's giving “tree update just happened, who's next?” energy. 🌈

💜 SEE ALSO 💜

Kernel file: ./block/bfq-wf2q.c

• bfq_gt(9)
• bfq_update_next_in_service(9)
• bfq_delta(9)
• bfq_calc_finish(9)
• bfq_entity_of(9)
• bfq_extract(9)
• bfq_idle_extract(9)
• bfq_insert(9)
• bfq_update_min(9)
• bfq_update_active_node(9)
• bfq_update_active_tree(9)
• bfq_active_insert(9)
• bfq_ioprio_to_weight(9)
• bfq_weight_to_ioprio(9)
• bfq_find_deepest(9)
• bfq_active_extract(9)
• bfq_idle_insert(9)
• bfq_forget_entity(9)
• bfq_put_idle_entity(9)
• bfq_forget_idle(9)
• bfq_bfqq_served(9)
• bfq_bfqq_charge_time(9)
• __bfq_activate_entity(9)
• __bfq_requeue_entity(9)
• bfq_activate_requeue_entity(9)
• __bfq_deactivate_entity(9)
• bfq_deactivate_entity(9)
• bfq_calc_vtime_jump(9)
• bfq_first_active_entity(9)
• __bfq_lookup_next_entity(9)

Cute little footer moment: source/version is ./block, the date is October 2026, and the manual name is bfq_lookup_next_entity(9). Byeee, go read the kernel file bestie! 🫶✨