From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc htb stats
Date: Tue, 04 Feb 2003 16:37:55 +0000 [thread overview]
Message-ID: <marc-lartc-104437737116482@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104437510812943@msgid-missing>
On Tuesday 04 February 2003 17:30, David DeLauro wrote:
> On Tue, 4 Feb 2003 At 10:20 -0600, mabrown-lartc@securepipe.com Articulated:
> > 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
>
> Thanks Martin...
>
> I was running under the assuption that "bps" was bits/s and "Bps" was
> bytes/sec...
It's bit when there is bit, otherwise it's byte :)
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-02-04 16:37 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
2003-02-04 16:30 ` David DeLauro
2003-02-04 16:37 ` Stef Coene [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=marc-lartc-104437737116482@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