In this simple htb setup:
# tc -s -d class ls dev eth0
class htb 1:1 root rate 300000bit ceil 300000bit burst 1749b/8 mpu 0b overhead
0b cburst 1749b/8 mpu 0b overhead 0b level 7
Sent 13171835 bytes 13169 pkt (dropped 0, overlimits 0 requeues 0)
rate 45848bit 10pps backlog 0b 0p requeues 0
lended: 5272 borrowed: 0 giants: 0
tokens: -84429 ctokens: -84429
class htb 1:2 parent 1:1 prio 0 quantum 1500 rate 80000bit ceil 300000bit
burst 1639b/8 mpu 0b overhead 0b cburst 1749b/8 mpu 0b overhead 0b level 0
Sent 12243472 bytes 8787 pkt (dropped 0, overlimits 0 requeues 0)
rate 43264bit 6pps backlog 0b 0p requeues 0
lended: 3515 borrowed: 5272 giants: 0
tokens: -181860 ctokens: -86779
class htb 1:3 parent 1:1 leaf 30: prio 0 quantum 2750 rate 220000bit ceil
300000bit burst 1709b/8 mpu 0b overhead 0b cburst 1749b/8 mpu 0b overhead 0b
level 0
Sent 928363 bytes 4382 pkt (dropped 0, overlimits 0 requeues 0)
rate 3400bit 4pps backlog 0b 0p requeues 0
lended: 4382 borrowed: 0 giants: 0
tokens: 61291 ctokens: 46039
class prio 30:1 parent 30:
class prio 30:2 parent 30:
class prio 30:3 parent 30:
What does it mean when the leaf 1:2 class has a negative token/ctoken count?
I''m generating this traffic with a "wget --limit-rate=5000"
command.
My understanding is that this indicates the number of tokens available for
burst traffic, is that correct? How did it become negative? I thought that
when the bucket is empty, traffic is delayed until a token shows up, or
eventually dropped.