bfq_update_active_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ bfq_update_active_node(9) β€” like, the glow-up page for a node's min_start ✨

okay so before we even start: this is from the Kernel API Manual, section 9, and the whole page is literally about giving one lil red-black-tree node a lil refresh πŸ’… stay with me bestie, it's shorter than it looks.


🌸 NAME 🌸

bfq_update_active_node β€” recalculate min_start.

πŸŽ€ SYNOPSIS πŸŽ€

void bfq_update_active_node (struct rb_node *node );

πŸ’– ARGUMENTS πŸ’–

  • node β€” the node to update. that's it. that's the whole argument list, she's low maintenance 🫢

✨ DESCRIPTION ✨

so here's the vibe check: node may have changed position, or one of its children may have moved. when that happens, this function swoops in and updates its min_start value 🧚

and here's the important part β€” a precondition, not a suggestion: the left and right subtrees are assumed to hold a correct min_start value. the function is trusting you on that fr fr. it's not re-checking the kids, it's just fixing up the parent's number πŸ’…

ngl this one is the "recompute after the tree shifted" helper, and it assumes the subtrees underneath are already slaying correctly before you call it πŸ‘‘

🌈 SEE ALSO 🌈

Kernel file ./block/bfq-wf2q.c β€” and the whole extended friend group:


and that's the whole page, bestie πŸ“ sign-off time: this lil number lives under the ./block source, dated October 2026, and yes it's bfq_update_active_node(9) again because we always bring it back to her πŸ‘‘βœ¨ iykyk πŸ’œ

πŸ“¦ where this page comes from