htb_charge_class(9)

📦 version 7.3.1, in nixpkgs unstable

💅 htb_charge_class(9) — like, the Kernel API Manual, bestie 🎀

okay so real talk, this one lives in the kernel API manual and it's genuinely iconic if you're into traffic shaping. it's htb_charge_class, and she's out here doing the actual accounting work. no cap.

✨ NAME ✨

htb_charge_class — charges amount "bytes" to leaf and ancestors 🧚

like, she literally takes the byte count and puts it on the books for the leaf class and everybody up the family tree. accountants could never.

🌸 SYNOPSIS 🌸

void htb_charge_class (struct htb_sched *q , struct htb_class *cl , int
level , struct sk_buff *skb );

that's the whole signature, bestie — void, so she doesn't return anything, she just does. main character energy fr fr 💅

🦋 ARGUMENTS 🦋

  • q — the priority event queue. this is the group chat where all the priority stuff is happening.
  • cl — the class to start iterate. yes, "start iterate" — that's the original wording and i'm not touching it, it's giving ancient scroll. this is where the walk begins 🚶‍♀️
  • level — the minimum level to account. the cutoff line. below this, we don't wanna hear it.
  • skb — the socket buffer. the packet itself, the celebrity of the whole operation 👑

💜 DESCRIPTION 💜

okay so here's the vibe: the routine assumes that a packet "bytes" long was dequeued from the leaf cl, and that it was borrowing from "level". like, that's the premise, she's not double-checking you on it. 🙈

given that, she:

  • accounts bytes to the ceil leaky bucket for the leaf and all ancestors — the whole lineage gets charged, no one escapes the group chat 💀
  • accounts to the rate bucket for ancestors at levels "level" and higher

and she also handles a possible change of mode resulting from the update. mode transitions are her whole thing, she's obsessed. ✨

⚠️ note that mode can also increase here (MAY_BORROW to CAN_SEND) — and the reason is lowkey so real: we can use a more precise clock than the event queue here. slay. accurate timing wins again ⏰

in that case — the mode-increasing one — we remove the class from the event queue first. order matters, bestie. you don't just barge in. you remove from the event queue first, then you do the thing. periodt.

🔥 SEE ALSO 🔥

the kernel file ./net/sched/sch_htb.c is the mothership, and here's her whole friend group — go say hi:

and that's the page!! 💖✨🎀🦋🌸

kisses from ./net/sched, dated October 2026 — catch you in the next manpage, bestie 🫶💜

📦 where this page comes from