From: Markus Schulz <msc@antzsystem.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb root don't reach ceil rate?
Date: Sat, 18 Feb 2006 18:24:24 +0000 [thread overview]
Message-ID: <200602181924.25045.msc@antzsystem.de> (raw)
In-Reply-To: <200602101445.27714.msc@antzsystem.de>
Am Freitag, 10. Februar 2006 14:45 schrieb Markus Schulz:
> tc -s -d class show dev ppp0
> class htb 1:1 root rate 576000bit ceil 576000bit burst 30Kb/8 mpu 0b
> overhead 0b cburst 1739b/8 mpu 0b overhead 14b level 7
> Sent 1485575598 bytes 3140554 pkts (dropped 0, overlimits 0)
> rate 480008bit 115pps
> lended: 1904616 borrowed: 0 giants: 0
> tokens: 385702 ctokens: -26458
ok, i've understand now. Differenz comes from gross versus net data
rates due to overhead of ATM-SAR and pppoe-overhead. All statistic
values are netto values.
--
Markus Schulz
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-02-18 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 13:45 [LARTC] htb root don't reach ceil rate? Markus Schulz
2006-02-18 18:24 ` Markus Schulz [this message]
2006-02-25 15:32 ` Andy Furniss
2006-02-25 15:42 ` 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=200602181924.25045.msc@antzsystem.de \
--to=msc@antzsystem.de \
--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