From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] more on cbq parameters ,further CBQ/tc doc,
Date: Mon, 10 Dec 2001 12:11:49 +0000 [thread overview]
Message-ID: <marc-lartc-100798634321233@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100796090708355@msgid-missing>
On Sun, Dec 09, 2001 at 09:06:47PM -0800, Don Cohen wrote:
> > On a 100Mbit card connected to a 256kbit line, I used something like:
> >
> > tc qdisc add dev eth0 root handle 1: cbq \
> > bandwidth 100Mbit avpkt 1000
> > tc class add dev eth0 parent 1:0 classid 1:1 cbq \
> > bandwidth 100Mbit rate 256kbit [...]
> > tc qdisc add dev eth0 parent 1:1 handle 10: cbq \
> > bandwidth 256kbit allot 1514 avpkt 1000
>
> This bandwidth (256 above) is NOT the physical device bandwidth.
These are cbq's within cbq's, for which there is generally no need.
When specifying 'bandwidth' with qdisc add, it *must* be the bandwidth of
the physical interface, or when the cbq is embedded within another cbq (ie,
when using 'tc qdisc add dev eth0 parent' as opposed to 'tc qdisc add dev
eth0 root'), it should be the bandwidth available to the class you attach it
to.
Because that bandwidth may not be fixed, embedding cbq's within cbq's rarely
makes sense.
Specifying 'bandwidth' with 'tc class add' only makes sense when specifying
minburst or maxburst, and is ONLY used for calculating those two, when
specified. You can safely omit it in fact. *If* specifying it, I'm not sure
if it should be:
o The rate of the parent class; or
o The bandwidth of the interface
> > bandwidth rate
> > This is different from the bandwidth specified when creating a CBQ disc. Only
> > used to determine maxidle and offtime, which are only calculated when
> > specifying maxburst or minburst. Mandatory if specifying maxburst or minburst.
>
> Great. So maybe you should tell us what the value is supposed to mean!
Maybe I should charge money. Do you see my point?
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-10 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 5:06 [LARTC] more on cbq parameters ,further CBQ/tc doc, Don Cohen
2001-12-10 5:22 ` Michael T. Babcock
2001-12-10 6:47 ` Stef Coene
2001-12-10 12:11 ` bert hubert [this message]
2001-12-10 13:48 ` Michael T. Babcock
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-100798634321233@msgid-missing \
--to=ahu@ds9a.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.