From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc htb stats
Date: Tue, 04 Feb 2003 16:20:21 +0000 [thread overview]
Message-ID: <marc-lartc-104437570113963@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104437510812943@msgid-missing>
David,
: When I look at the rate my cisco router
: reports for a 5min avg and I look at a calculated 5min average (30 polls
: of the tc once every 10sec) for tc they are very different. The cisco is
: reported as ~2090kb/s and tc reports my parent as ~251kb/s.
: Even if I take all the classes separately and add the averages together
: I get closer but not that much closer. Is my math wrong? How does the
: tc/htb qdisc figure the avg. rate?
$ expr 251 \* 8
2008
Snipped from http://www.docum.org/stef.coene/qos/docs/ :
"When you use the tc command, you have to remember that mb = 1024 kb 1024 * 1024 b = byte/s and that mbit = 1024 kbit = 1024 * 1024 bit bit/s."
Snipped from http://lartc.org/howto/lartc.qdisc.html :
"Just to prevent confusion, tc uses the following rules for bandwith
specification:
mbps = 1024 kbps = 1024 * 1024 bps => byte/s
mbit = 1024 kbit => kilo bit/s.
mb = 1024 kb = 1024 * 1024 b => byte
mbit = 1024 kbit => kilo bit.!
Are you certain your units are the same? Strangely, the tc command line
tool uses kb for kilobytes/second. I think 251 kilobytes-per-second is
quite close to 2090 kilobits-per-second.
Bye for now,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-04 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 16:10 [LARTC] tc htb stats David DeLauro
2003-02-04 16:20 ` Martin A. Brown [this message]
2003-02-04 16:30 ` David DeLauro
2003-02-04 16:37 ` Stef Coene
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-104437570113963@msgid-missing \
--to=mabrown-lartc@securepipe.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