From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB traffic shaping odd effects
Date: Mon, 09 Jan 2006 01:11:01 +0000 [thread overview]
Message-ID: <43C1B825.2000409@dsl.pipex.com> (raw)
In-Reply-To: <43BE1D93.2040409@anchor.com.au>
Oliver Hookins wrote:
> Denis Ovsienko wrote:
>
>>> tc qdisc add dev eth0 root handle 1: htb default 10
>>> tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbit burst 24k
>>
>>
>> Does the following help?
>> tc qdisc add dev eth0 root handle 1: htb default 1
>> tc class add dev eth0 parent 1: classid 1:1 htb rate 81mbit burst 24k
>
>
> That seems a bit backward, limiting the total available bandwidth to
> enforce child class limits. Or is that how htb works, that the sum of
> the child classes must add up to no less than the parent class?
>
> In any case we have 100mbit available so I don't want to set it any
> lower than that, if possible.
>
You haven't got 100mbit once overheads are accounted for and in this
test using 81 instead of 100 won't affect your bandwidth as all traffic
is going to one of the two sub classes. I have IIRC spotted differences
(to do with quantum and sharing excess) when parent is > than ceils - it
wasn't the same setup as yours though.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-09 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 7:34 [LARTC] HTB traffic shaping odd effects Oliver Hookins
2006-01-06 9:17 ` Denis Ovsienko
2006-01-08 23:13 ` Oliver Hookins
2006-01-09 1:06 ` Andy Furniss
2006-01-09 1:11 ` Andy Furniss [this message]
2006-01-09 2:44 ` Oliver Hookins
2006-01-09 17:41 ` Andy Furniss
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=43C1B825.2000409@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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.