From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB Quatum values
Date: Fri, 20 Feb 2004 12:56:47 +0000 [thread overview]
Message-ID: <200402201356.47732.stef.coene@docum.org> (raw)
In-Reply-To: <403598A8.4090509@snapgear.com>
On Friday 20 February 2004 06:18, Damion de Soto wrote:
> Hi guys,
>
> I've just been playing and reading again, and come to the conclusion
> that although i've read a lot about quantum (& r2q) settings for the
> htb qdisc, i still don't understand it.
>
> If the quantum for each class should be as small as possible, but
> larger than the MTU, then is there any reason I shouldn't always
> set it to the MTU size ?
Yes. Each class will be able to send quantum bytes. If quantum is too low,
the classes are maybe not able to send enough packets because the polling
frequency is not high enough.
> If 2 classes are fulfulling their rate and you want them to share
> unequally, instead of making the quantums different of each one, why not
> just change the prio ?
The prio does 2 things :
- a low prio class will have low latency if this class is not overlimited,
but if this class is overlimited, the latency can be very high
- a low prio class will have a higher priority to borrow tokens from the
parent class
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-02-20 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 5:18 [LARTC] HTB Quatum values Damion de Soto
2004-02-20 12:56 ` 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=200402201356.47732.stef.coene@docum.org \
--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.