Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and theory
Date: Mon, 09 Dec 2002 22:18:52 +0000	[thread overview]
Message-ID: <marc-lartc-103947246114318@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103945416224487@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]

Hi Stef!

> > I'll let HTB to automatically compute the values for 'burst' and
> > 'cburst'. The problem is elsewhere. What are the correct values for
> > 'rate' and 'ceil' of 11:2 class in this case? In fact, total value of
> > 'ceil's from all sub-classes exceeds 5000Kbit, so there are moments when
> > the bandwidth that comes from my ISP is bigger than guaranteed bandwidth.
> > Is there some kind a theory that says how to establish the values of
> > 'rate's and 'ceil's from the parent and its sub-classes?
> There are some rules : ceil of child <= ceil of parent, sum (child rates) <= 
> rate of parent ....  You don't have to follow this rules, but the final 
> shaping result can be strange.
> See the faq page on www.docum.org.

What would be nice is if you could document what happens when

     a) child ceil > parent ceil
     b) child rate > parent ceil
     c) child ceil > parent rate
     d) child rate > parent rate

How does this influence the shaping results and the shaping of other
classes? I've actually asked a similar question before: If you have

           1:1
           / \
         /     \
       1:2     1:3
       /|\       \------
     /	|  \       \     \
   1:4 1:5 1:6     1:7   1:8

if 1:7 and 1:8 respects the rate/ceil of 1:3 and 1:3 respects the rate/ceil
of 1:1, but 1:4 does not respect the rate/ceil of 1:2 and 1:2 respects the
rate/ceil of 1:1, does the shaping of 1:3 work as normal and only those
classes under 1:2 are adversely affected or not? from your previous answer,
it seems that the classes under 1:3 would not be affected, but I would love
to know why. what happens with 1:4 requests some bandwidth which 1:2 does
not have...


-- 

Regards
 Abraham

NEWARK has been REZONED!!  DES MOINES has been REZONED!!

___________________________________________________
 Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
 P.O. Box 3472, Matieland, Stellenbosch, 7602
 Cell: +27 82 565 4451 Http: http://www.frogfoot.net/
 Email: abz@frogfoot.net


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-12-09 22:18 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 [this message]
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
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-103947246114318@msgid-missing \
    --to=abz@frogfoot.net \
    --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