From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and theory
Date: Thu, 12 Dec 2002 11:19:43 +0000 [thread overview]
Message-ID: <marc-lartc-103969212018812@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103945416224487@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
Hi Stef!
> I did some small tests :
[snip]
> Conclusion : if you want to know how traffic will be shaped, you have to
> follow some basic rules.
> I will update docum.org tonight.
You're right. I did some tests this weekend as well and realised that you
have to stick with the basics. The problem was that it was not so clear to
me how HTB behaves when the child's rates/ceil exceed the parent's.
Some other questions I'd like to ask you while I'm at it:
1) if you have:
1:1
/ \
/ \
1:2 1:3
/ \ / \
/ \ / \
1:4 1:5 1:6 1:7
If
1:2 = prio 1
1:3 = prio 2
1:4 = prio 10
1:5 = prio 11
1:6 = prio 5
1:7 = prio 6
Is 1:4, 1:5 evaluated first or 1:6, 1:7? Iow, does HTB start at the root
node, prioritize its children and, subprioritize their children, etc. or
is only the leaf nodes' priorities important (i.e. 1:6, 1:7, 1:4, 1:5)
2) if a class is evaluated and there is some bandwidth available to borrow,
is the first non-congested child given all bandwidth that is available and
then the next is given the rest and so on or is each child given a quantum
of bandwidth, then if there is some bandwidth left, a second round and so on?
--
Regards
Abraham
History repeats itself. That's one thing wrong with history.
___________________________________________________
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 --]
next prev parent reply other threads:[~2002-12-12 11:19 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
2002-12-12 11:19 ` Abraham van der Merwe [this message]
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-103969212018812@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