Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] negative token/ctokens
Date: Wed, 15 Mar 2006 03:54:17 +0000	[thread overview]
Message-ID: <44178FE9.B25CAA30@iswest.com> (raw)
In-Reply-To: <200603081046.51747.ahasenack@terra.com.br>

Andreas Hasenack wrote:
> 
> 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
> 
> What does it mean when the leaf 1:2 class has a negative token/ctoken count?

Maybe this will help:
http://www.docum.org/docum.org/docs/htb/
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2006-03-15  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 13:46 [LARTC] negative token/ctokens Andreas Hasenack
2006-03-15  3:54 ` gypsy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44178FE9.B25CAA30@iswest.com \
    --to=gypsy@iswest.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox