From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB rate 0kbit
Date: Mon, 20 Jan 2003 17:54:35 +0000 [thread overview]
Message-ID: <marc-lartc-104308532712311@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104220082605034@msgid-missing>
On Monday 20 January 2003 18:43, Catalin Bucur wrote:
> Abraham van der Merwe wrote:
> | Hi Thomas!
> |
> | The smallest rate you can use with r2q=1 is mtu*8 kbit (12kbit in most
> | cases). You can skip r2q and use quantum\x125 bytes, but that is
>
> probably not
>
> | such a good idea...
> |
> |>OK, I will use rate 1kbit. Therefore r2q should be 1, right?
> |>
> |> Thanks,
> |> Thomas
>
> The HTB FAQ page from Devik's site says that you should use at least
> 4kbit for realiable operation of HTB. So it's hard to say what could be
> the best minimal quantum value in this case. It's not a good ideea to
> use a value smaller than 1500 bytes, so leave the quantum at this value
> and ignore the warning messages from syslog, or use the patch against
> 2.4.20 to skip these type of errors.
Quantum must be > 1500 so the internal caculations of htb are good.
And 60.000 is the maximum hard coded in htb.
So try to take r2q so
smallest_rate/r2q > 1500
biggest_rate/r2q < 60000
Quatum is only used if you have a parent class that's has remaining bandwidth.
I don't know if this is the case in your situation.
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/
prev parent reply other threads:[~2003-01-20 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 12:12 [LARTC] HTB rate 0kbit Thomas Jalsovsky
2003-01-10 16:02 ` Catalin Bucur
2003-01-20 8:55 ` Thomas Jalsovsky
2003-01-20 11:52 ` Abraham van der Merwe
2003-01-20 17:43 ` Catalin Bucur
2003-01-20 17:54 ` Stef Coene [this message]
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-104308532712311@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 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.