All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB classes: is it true that the rate of a parent MUST
Date: Wed, 21 May 2003 02:53:17 +0000	[thread overview]
Message-ID: <marc-lartc-105348563909365@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105326543109245@msgid-missing>

 : >  : 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.

Hmmmm.....I think I see my error.  But I think we have an challenge in
accurately describing it.  So, to be unbelievable verbose:

  If the parent class "ceil" parameter matches (or is greater than) the
  sum of the "ceil" parameter for all of the leaf children (terminal
  HTB children), then there is no way for this parent's "ceil" to be
  exceeded.

This definition is halfway between the "maximum of all the ceil
parameters of the children classes" and the "total of all of the ceil",
both of which are inaccurate in different ways.  Do you agree, Stef?

( Martin wonders if Stef enjoys splitting hairs. )

 : 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.

Agreed.

 : > 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.

Ah-ha!  This makes sense.  Thanks for the clarification.

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-05-21  2:53 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 ` [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-21  2:53 ` Martin A. Brown [this message]
2003-05-22 21:09 ` 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-105348563909365@msgid-missing \
    --to=mabrown-lartc@securepipe.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.