From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What happens when guaranteed BW cannot be delivered (HTB and CBQ)
Date: Tue, 12 Nov 2002 16:15:05 +0000 [thread overview]
Message-ID: <marc-lartc-103711794428215@msgid-missing> (raw)
On Tuesday 12 November 2002 13:43, Mathieu Deziel wrote:
> > But the settings
> > like rate and burst are satisified even if there is less bandwidth
> > available then configured.
>
> How can the rate be satisfied, when it is not physically available?
My mistake.
Each class will get bandwidth proportional to the rate untill all the rates
are satisfied or there is no bandwidth left. Remaining bandwidth is given to
the class with the lowest priority and proportional to the quantum parameter.
One of the rules if you create a htb setup, is to make the sum of the rates of
the child classes <= rate of the parent class. So the rate can always be
satisfied. You don't have to follow this rule, htb will work fine, but it
will no be obviously to know what's going on.
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 reply other threads:[~2002-11-12 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 16:15 Stef Coene [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 19:33 [LARTC] What happens when guaranteed BW cannot be delivered (HTB and CBQ) Mathieu Deziel
2002-11-08 22:58 ` 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-103711794428215@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.