From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB classes: is it true that the rate of a parent MUST be exactly equal to the sum of ra
Date: Sun, 18 May 2003 18:24:17 +0000 [thread overview]
Message-ID: <marc-lartc-105328234720621@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105326543109245@msgid-missing>
On Sunday 18 May 2003 19:27, Martin A. Brown wrote:
> Miernik,
>
> I'll add a bit to Stef's answer.
:)
> : When configuring HTB classes, is it true that the rate of a parent
> : MUST be exactly equal to the sum of rates of it's children?
>
> No. This is not true. This is merely a recommendation for how to use
> HTB. When the parent class ceil matches the total of all of the ceil
> parameters of the children classes, there is no way for bandwidth usage to
> exceed the parent ceil.
It's not the "total of all of the ceil", it's the maximum of all the ceil
parameters of the children classes.
And you can exceed the parent ceil. See me other post on this subject. It
can because the rate of a class is the minimum the class always gets. Even
if it exceeds the parent ceil.
> : For example let's say I have a 160Kbit link, and two clients. I want
> : each of them to have equal transfer rate, and ceil each of them to
> : 70Kbit. I leave 5% of the link idle as suggested on
> : http://www.docum.org/stef.coene/qos/faq/cache/9.html
>
> I have a clarification to make, which may help you understand all of the
> answers to your questions:
>
> With HTB, shaping is only performed by the leaf class. Why
> bother setting rate and ceil in parent classes? The ceil is
> used by the parent class to lend bandwidth to the child
> classes [1]. In short, all non-leaf classes use ceil to cap how
> much bandwidth to lend to a child class.
This is true for the ceil. But not for the rate. The rate of the parent
class is used to split the traffic. See other post on the same subject for
an example. And I just realized that I stated before that the parent rate is
never respected. That's not true. It is. But I don't know how exactly.
> I would disagree with Stef (note, Stef *does* have more experience with
> HTB, so let's see what he says). These setups are not equivalent.
Thx ;)
> Miernik--I would recommend this type of approach. In your example,
> though, you are using a rate which is below Devik's recommend minimum rate
> for reliable operation of HTB [2]. Perhaps you could create 25 classes,
> and put two IPs in each class. That gives you a 6kbit rate for each child
> class.
I think Devik means that this is a minimu rate for active classes. And he
states that there are only some of the classes active. So the real rate will
always > 6kbit. As long as quantum is big enough, I don't think there will
be a problem.
I deleted some parts of Martins answer. My conclustion : I need to do some
more tests to find out how the parent settings influence the children.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-18 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 10:39 [LARTC] HTB classes: is it true that the rate of a parent MUST be exactly equal to the sum of rates Miernik
2003-05-18 14:14 ` [LARTC] HTB classes: is it true that the rate of a parent MUST be exactly equal to the sum of ra Stef Coene
2003-05-18 17:27 ` [LARTC] HTB classes: is it true that the rate of a parent MUST Martin A. Brown
2003-05-18 18:24 ` Stef Coene [this message]
2003-05-21 2:53 ` Martin A. Brown
2003-05-22 21:09 ` [LARTC] HTB classes: is it true that the rate of a parent MUST be exactly equal to the sum of ra Stef Coene
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-105328234720621@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.