From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] more on cbq parameters
Date: Sun, 09 Dec 2001 22:28:44 +0000 [thread overview]
Message-ID: <marc-lartc-100793697008454@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100774185824127@msgid-missing>
On Sat, Dec 08, 2001 at 09:10:50PM +0100, bert hubert wrote:
> > Notice above I supplied bandwidth 30kbit which is far from the actual
> > physical bandwidth (100Mbit). Maybe this is why I get good results.
> > Maybe this is what you're SUPPOSED to do!
>
> Not that I'm aware of.
To agree with you, AFAICS, the correct way to deal with this is to specify
the root bandwidth as the maximum physical bandwidth on the interface, then
split it down using classes that have rates set to the expected rates.
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
(PS, highly inspired by Stef and others' scripts of course)
All my other classes then hang off 10: instead of 1: and work quite well.
What I've considered doing a few times is adding an option to dump out
the values CBQ is looking at for idleness at each level as well as
dynamic avpkt values (based on reality).
HTB may do this, of course.
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-09 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 16:15 [LARTC] more on cbq parameters Don Cohen
2001-12-07 16:40 ` Martin Devera
2001-12-08 20:10 ` bert hubert
2001-12-09 22:28 ` Michael T. Babcock [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-100793697008454@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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