From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb2 with link sharing - the bandwidth dividing question
Date: Sun, 29 Sep 2002 20:33:44 +0000 [thread overview]
Message-ID: <marc-lartc-103333169707710@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102732759808222@msgid-missing>
On Monday 23 September 2002 05:29, Adi Nugroho wrote:
> On Wednesday 24 July 2002 02:49, Stef Coene wrote:
> > Actually, the remaining bandwidth is not divided proportional to the
> > rate, but to quantum.
>
> Helo....
> I would like to ask about r2q and quantum.
> I'm using sfq, which has also something named quantum.
> the question is....
> I I want that the remaining bandwidth to be devided proportional to the
> rate, which one shuld I set...
> * sfq quantum?
> * or htb quantum?
> * or both?
Htb quantum is used to between different classes and only for bandwidth that
remains after each class get's it's rate.
Sfq quantum is used within one class where the sfq qdisc is attached to and
determines how many bytes each flow can send when they may send.
Setting on quantum is the best.
> Second question, how can we set r2q lower than 1? I would like to set my
> r2q to 0.1.
Just try it out. I don't know if it will work.
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:[~2002-09-29 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 8:44 [LARTC] htb2 with link sharing - the bandwidth dividing question Lumir Unzeitig
2002-07-22 14:38 ` Stef Coene
2002-07-23 9:26 ` Lumir Unzeitig
2002-07-23 18:49 ` Stef Coene
2002-09-23 3:29 ` Adi Nugroho
2002-09-29 20:33 ` 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-103333169707710@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.