Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Need help with HTB
Date: Tue, 28 Oct 2003 21:05:10 +0000	[thread overview]
Message-ID: <marc-lartc-106737719423583@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106729452827597@msgid-missing>

On Tuesday 28 October 2003 21:38, Mihai Tanasescu wrote:
> This is the output I get from tc -s -d class show dev eth0 and eth1:
>
> serv:~# tc -s -d class show dev eth0
>
> class htb 1:99 parent 1:1 leaf 990: prio 7 quantum 2560 rate 20Kbit ceil
> 90Kbit burst 1624b/8 mpu 0b cburst 1714b/8 mpu 0b level 0
>  Sent 4693480 bytes 28021 pkts (dropped 0, overlimits 0)
>  rate 470bps 2pps
>  lended: 26883 borrowed: 1138 giants: 0
>  tokens: 502079 ctokens: 117973
>
> class htb 1:1 root rate 100Kbit ceil 100Kbit burst 1727b/8 mpu 0b cburst
> 1727b/8 mpu 0b level 7
>  Sent 38956319 bytes 489172 pkts (dropped 0, overlimits 0)
>  rate 1771bps 18pps
>  lended: 2994 borrowed: 0 giants: 0
>  tokens: 101376 ctokens: 101376
>
> class htb 1:2 parent 1:1 prio 1 quantum 2560 rate 20Kbit ceil 20Kbit
> burst 1624b/8 mpu 0b cburst 1624b/8 mpu 0b level 0
>  Sent 33941 bytes 221 pkts (dropped 0, overlimits 0)
>  lended: 221 borrowed: 0 giants: 0
>  tokens: 333119 ctokens: 333119
>
> class htb 1:3 parent 1:1 leaf 30: prio 3 quantum 7680 rate 60Kbit ceil
> 90Kbit burst 1675b/8 mpu 0b cburst 1714b/8 mpu 0b level 0
>  Sent 34228898 bytes 460930 pkts (dropped 0, overlimits 0)
>  rate 1362bps 17pps
>  lended: 459074 borrowed: 1856 giants: 0
>  tokens: 163413 ctokens: 111717
>
> serv:~# tc -s -d class show dev eth1
>
>
> class htb 2:99 parent 2:1 leaf 299: prio 5 quantum 3840 rate 30Kbit ceil
> 90Kbit burst 1637b/8 mpu 0b cburst 1714b/8 mpu 0b level 0
>  Sent 109217144 bytes 335470 pkts (dropped 0, overlimits 0)
>  rate 1927bps 13pps
>  lended: 277195 borrowed: 58275 giants: 0
>  tokens: 244309 ctokens: 103297
>
> class htb 2:1 root rate 100Kbit ceil 100Kbit burst 1727b/8 mpu 0b cburst
> 1727b/8 mpu 0b level 7
>  Sent 172060944 bytes 480526 pkts (dropped 0, overlimits 0)
>  rate 2186bps 14pps
>  lended: 68187 borrowed: 0 giants: 0
>  tokens: 96257 ctokens: 96257
>
> class htb 2:2 parent 2:1 prio 1 quantum 8960 rate 70Kbit ceil 90Kbit
> burst 1688b/8 mpu 0b cburst 1714b/8 mpu 0b level 0
>  Sent 62843800 bytes 145056 pkts (dropped 18, overlimits 0)
>  rate 259bps
>  lended: 135144 borrowed: 9912 giants: 0
>  tokens: 150034 ctokens: 118543
I'm afraid it's not so easy to get better results.  You allmost have no 
borrowed packets so none of your classes are over limited. And tokens/ctokens 
is never negative so you have tokens enough to send something.

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-10-28 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 22:37 [LARTC] Need help with HTB Mihai Tanasescu
2003-10-28 18:12 ` Stef Coene
2003-10-28 20:38 ` Mihai Tanasescu
2003-10-28 21:05 ` Stef Coene [this message]
2003-10-29  0:32 ` Andy Furniss

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=marc-lartc-106737719423583@msgid-missing \
    --to=stef.coene@docum.org \
    --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