From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How HTB treats priorities?
Date: Sun, 05 Jan 2003 17:42:07 +0000 [thread overview]
Message-ID: <marc-lartc-104178860708480@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104110872106366@msgid-missing>
On Saturday 04 January 2003 21:21, ISC Robert Krycza³o wrote:
> Hello Stef,
Hi,
I have 1 big remark. You results are incorrect and not usable. The quantum
of your class is too low. You have a rate of 1kbit, so quantum is 1kbit / 10
= 100 bit. In your case, quantum is important. Each class may send quantum
bytes to use all remaining bandwidth from the parent. Let's say class 21 and
22 are fighting for bandwidth. The qauntums are 400 and 300. So class 21
may send 400bit and after that class 22 may send 300bit. But most packets
are 1500byte !!! So 1500 byte is sended. So the internal calulations of
htb are totally fucked up (sorry for the language :).
If you want to get some good results, use at minimum a rate of 15kbit or
change the r2q parameter. If you are curious about the qauntum parameter, I
have some more info on www.docum.org on the faq page.
I redid some of your test with higher rates. I multiplied the rates with 16
(so kbit -> kpbs and x2). And I added r2q = 1 so lowest quantum is
2000bytes.
And I toke a wrong conclusion. The parent ceil is not respected IF the sum of
the rates of childs exceed the parent ceil. So if you have 2 childs classes
with rate = 100 and a parent ceil of 100, the parent ceil is not respected
and the childs will get each 100. But if you have 2 class with rate = 2 and
parent ceil = 100, then the childs to gether will never get more then 100.
So the parent ceil is respected.
Traffic in class 21 : 127.5 KB/s
Traffic in class 22 : 256.1 KB/s
Traffic in class 21 and 22 : 120.4 KB/s and 137.7 KB/s
so the parent ceil is respected. But I still don't know how the traffic is
divided. The sum is 258.1 so class 21 gets 46.6%. I think each class gets
the configured rate and the remaining traffic is splitted 50-50.
> During the tests I discovered that in case of root class (1:0 in my
> example) only rate matters not ceil. I accidentally changed 1:2 and 1:3 to
> root classes and then 22,23,24 were limited to 8kbit/s.
I did the same. And indeed. For a root class, ceil = rate even if you
specify a higher ceil. Strange. On the other hand, it's logic to create 1
root class that holds all traffic so it has rate = ceil. It's the
"bottleneck" within the htb structure.
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-01-05 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 20:53 [LARTC] How HTB treats priorities? ISC Robert Kryczało
2002-12-29 5:01 ` Stephane Ouellette
2002-12-29 23:23 ` Stef Coene
2002-12-30 22:35 ` ISC Robert Kryczało
2002-12-30 23:37 ` Stef Coene
2003-01-02 16:26 ` Homer Parker
2003-01-02 17:56 ` ISC Robert Kryczało
2003-01-02 18:03 ` ISC Robert Kryczało
2003-01-02 21:57 ` Stef Coene
2003-01-04 20:21 ` ISC Robert Kryczało
2003-01-05 17:42 ` Stef Coene [this message]
2003-01-06 18:54 ` ISC Robert Kryczało
2003-01-06 19: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-104178860708480@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