From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ inaccuracy
Date: Thu, 13 Dec 2001 08:20:32 +0000 [thread overview]
Message-ID: <marc-lartc-100823175116468@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100820629913063@msgid-missing>
On Thursday 13 December 2001 08:50, you wrote:
> On Thu, 13 Dec 2001, bert hubert wrote:
> > On Wed, Dec 12, 2001 at 07:17:43PM -0600, Amit Kucheria wrote:
> > > I have found CBQ to be very inaccurate (as others on the list)
> > >
> > > I have created a structure as follow
> > >
> > > Root (10mbit)
> > >
> > > CBQ class (bandwidth=1mbit, rate=10mbit)
> > >
> > > CBQ qdisc (bandwidth=1mbit)
> >
> > 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
>
> ---------------------------------------------------------------------------
> BANDWIDTH=bandwidth 10Mbit
> LIMITBW=1Mbit
>
> # Root CBQ qdisc 1:
> $TC qdisc add $DEVICE root handle 1: cbq $BANDWIDTH $AVPKT
>
> # Root CBQ class 1:1
> # This class rate limits everyting to 1Mbit
> $TC class add $DEVICE parent 1:0 classid 1:1 cbq $BANDWIDTH rate $LIMITBW
> \
> maxburst 100 $AVPKT allot 1514 weight 100Kbit prio 1 bounded isolated
>
> # Filter packet from the 2 sources
> $TC filter add $DEVICE parent 1: protocol ip prio 1 u32 match ip src
> $SRC1 flowid 1:1
> $TC filter add $DEVICE parent 1: protocol ip prio 1 u32 match ip src
> $SRC2 flowid 1:1
>
> # CBQ qdisc 2:0
> $TC qdisc add $DEVICE parent 1:1 handle 2:0 cbq bandwidth $LIMITBW $AVPKT
> allot 1514
> -------------------------------------------------------
I'm not seeing any big errors. I tried also the bounded parameter of CBQ,
you can find the results on docum.org. I was able to throttle the bandwidth
at each speed I want. I din't attach the second CBQ, but only used the
bounded class, maybe you can try again without the second CBQ.
And don't use the isolated parameter. It's not working and sometimes it can
disturb the configuration.
Stef
--
stef.coene@docum.org
More QOS info : http://docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
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-13 8:20 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 [this message]
2001-12-13 8:49 ` bert hubert
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-100823175116468@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 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.