From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ inaccuracy
Date: Thu, 13 Dec 2001 08:49:04 +0000 [thread overview]
Message-ID: <marc-lartc-100823342119307@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100820629913063@msgid-missing>
On Thu, Dec 13, 2001 at 09:20:32AM +0100, Stef Coene wrote:
> > > Um, this doesn't make sense. I keep repeating this to posters here, SHOW
> > > YOUR CONFIGURATION! Don't just draw pictures - your CBQ commandlines may
> > > not do what you think they do.
> >
> > My apologies. Here's the script
Amit, no apologies are needed, it's just that it helps to get good answers
:-)
> > # CBQ qdisc 2:0
> > $TC qdisc add $DEVICE parent 1:1 handle 2:0 cbq bandwidth $LIMITBW $AVPKT
> > allot 1514
Just don't do this. Having a CBQ within a CBQ is useless and can indeed
cause weird behaviour. You will get two qdiscs 'stacked' so to speak, both
trying to shape traffic. At times, the inner qdisc will not want to give up
data, which doesn't make life easier on the outer one.
CBQ can do shaping out of its own accord - it doesn't need a second shaper
to do that for it. For the same reasone, people should not embed TBFs in
CBQ!
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/
prev parent reply other threads:[~2001-12-13 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 1:17 [LARTC] CBQ inaccuracy Amit Kucheria
2001-12-13 7:14 ` bert hubert
2001-12-13 7:50 ` Amit Kucheria
2001-12-13 8:20 ` Stef Coene
2001-12-13 8:49 ` bert hubert [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-100823342119307@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.