bfq_forget_entity(9)

📦 version 7.3.1, in nixpkgs unstable

💖 bfq_forget_entity — the kernel API manual, bestie edition 💖

okay so real talk, this is a page from the <pink>Kernel API Manual</pink> and it's called bfq_forget_entity. yes we're in the scheduler guts. yes it's giving main character energy. let's go 🫶

✨ NAME ✨

bfq_forget_entity — literally means do not consider entity any longer for scheduling. like, we're done here, entity. bye. 👋

✨ SYNOPSIS ✨

void bfq_forget_entity (struct bfq_service_tree *st , struct bfq_entity
*entity , bool is_in_service );

she takes three things and returns void, no cap. 💅

✨ ARGUMENTS ✨

  • st — the service tree. that's her. 🌳
  • entity — the entity being removed. it's getting uninvited from the party 🎀
  • is_in_service — a bool, and it's true if entity is currently the in-service entity. iykyk 🔥

✨ DESCRIPTION ✨

okay so first thing: forget everything about entity. like fully. 🧠💨

and in addition to that — here's the part people miss — if entity represents a queue, and that queue is not in service, then we release the service reference to the queue. you know, the one taken through bfq_get_entity. 💀

fr fr, in this case there is really no more service reference to the queue, because the queue is also outside any service tree. it's free. it's unbothered. it's not on the tree. 🌸

if, instead, the queue is in service? then __bfq_bfqd_reset_in_service will take care of putting the reference when the queue finally stops being served. so like, not your problem, bestie, someone else is handling it. 🫶

⚠️ tiny vibe check: two different code paths here depending on whether the queue is in service. don't mix them up or you'll leak a reference and that's not slay. 😭

✨ SEE ALSO ✨

kernel file ./block/bfq-wf2q.c — go read it, it's iconic 👑

the whole friend group:

and that's the whole page, bestie!! 💖✨🎀🦋🌸💅🫶

this lil beauty comes to you from <purple>./block</purple>, dated <cyan>October 2026</cyan>. mwah, go forth and forget some entities 💜👑

📦 where this page comes from