Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and theory
Date: Thu, 12 Dec 2002 10:49:56 +0000	[thread overview]
Message-ID: <marc-lartc-103969031917322@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103945416224487@msgid-missing>

On Thursday 12 December 2002 09:36, Abraham van der Merwe wrote:
> Hi Stef!
> I think your explanation of "rate of class" in your FAQ is wrong. it
> caught me as well, but from devik's faq page
> (http://luxik.cdi.cz/~devik/qos/htb/htbfaq.htm):
>
> ------------< snip <------< snip <------< snip <------------
> What if sum of child rates is greater than parent rate ?
>
> Then interesting things can happen. Total rate delivered by children can be
> higher that parent's rate (thus its rate is not respected). However when
> sum of actual child rates are under parent's rate then borrowing will occur
> like in regular case.
>
> ------------< snip <------< snip <------< snip <------------
>
> Thus, if sum (rate of childs) > parent rate, then the parent rate is _not
> respected_.
:)
Devik is right, I'm wrong.  Do you know why I was convinced that my rule was 
OK?  Because I always followed my own rules :)

I did some small tests :


             ceil rate
1            200  200
 \- 10       200  100
     \- 100  200  100
     \- 101  200  100
 \- 20       200  100

Traffic in 100, 101 and 20 : each gets 67 (33%)
        Parent rate (10) is not respected otherwise 10 should share 50% with 
20.
Traffic in 100 and 20 : each gets 100 (50%)

If you respect "sum (rate of childs) = parent rate" it works like expected :

             ceil rate
1            200  200
 \- 10       200  100
     \- 100  200  50
     \- 101  200  50
 \- 20       200  100

Traffic in 100, 101 and 20 : 20 gets 100 (50%), 101 50 (25%) and 101 50 (25%).
Traffic in 100 and 20 : each gets 100 (50%)


Conclusion : if you want to know how traffic will be shaped, you have to 
follow some basic rules.
I will update docum.org tonight.

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/

  parent reply	other threads:[~2002-12-12 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 17:14 [LARTC] HTB and theory Catalin Bucur
2002-12-09 18:22 ` Stef Coene
2002-12-09 20:27 ` Catalin Bucur
2002-12-09 21:22 ` Stef Coene
2002-12-09 21:45 ` Catalin Bucur
2002-12-09 22:18 ` Abraham van der Merwe
2002-12-10 12:33 ` Stef Coene
2002-12-10 12:40 ` Stef Coene
2002-12-10 13:28 ` Abraham van der Merwe
2002-12-10 21:23 ` Stef Coene
2002-12-12  8:36 ` Abraham van der Merwe
2002-12-12 10:49 ` Stef Coene [this message]
2002-12-12 11:19 ` Abraham van der Merwe
2002-12-12 18:32 ` 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-103969031917322@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox