From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] quantum vs. r2q ?
Date: Thu, 01 May 2003 09:20:33 +0000 [thread overview]
Message-ID: <marc-lartc-105178135727071@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105177382822634@msgid-missing>
On Thursday 01 May 2003 09:17, openings wrote:
> Thanks for your answer. stef.
>
> My exmaple is not suitable.
>
> but, On 100Mbit Ethernet Network environment.
>
> Some class's rate can be 1Mbps.
>
> The other class's rate can be 30Mbps
>
> In this situation, when r2q\x10, automatic set quantum value = 12500 (1Mbps
> class) automatic set quantum value = 375000(30Mbps class) => too big!
>
> when r2q\x100, automatic set quantum value = 1250
> (1Mbps class)=> too small! automatic set quantum value = 37500 (30Mbps
> class)
>
> when r2q P, automatic set quantum value = 2500
> (1Mbps class) automatic set quantum value = 75000 (30Mbps class)=> too
> big!
>
> Searching of r2q value is too difficult.
>
> In above situation,
> I select r2q = 50, and when I create 30Mbps class, I use quantum0000
> option. Is this right?
Yes. But don't worry about a wrong quantum. It's only used when 2 classes
are asking for more bandwidth then the rate.
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-05-01 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 7:17 [LARTC] quantum vs. r2q ? openings
2003-05-01 9:20 ` 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-105178135727071@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.