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: Fri, 08 Nov 2002 22:58:43 +0000 [thread overview]
Message-ID: <marc-lartc-103679638205765@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103678409424931@msgid-missing>
On Friday 08 November 2002 20:33, Mathieu Deziel wrote:
> Hi all,
>
> Suppose you have the following hypothetical scenario.
> Your traffic enters the root queue (HTB or CBQ). Then, traffic is
> subdivided into level 2 classes. Some of the level 2 classes are
> subdivided further into level 3 classes.
> This is all done according to some filters (this is not the point here,
> though).
>
> [L1 Root]
>
> L2 L2
> / \
> L3 L3
>
> Of course, all the leaf classes are configured to a given "base" or
> "guaranteed" rate.
> The sum of these guaranteed rate does not exceed the total available
> bandwidth".
> The sum of the base rates of the children of a class does not exceed the
> base rate of the parent.
> Also, if other queues are not using their base BW, their available BW
> can be borrowed by other, up to "the total available bandwidth"
> Specifically, if we are using HTB, the ceil of each class would be set
> to the "the total available bandwidth"
>
> Now, on some medium, it is hard to evaluate in advance the available
> bandwidth on the link.
> For example, on Ethernet, when there is a lot of traffic, the available
> BW for a node can become low.
>
> Lets say that this is what happens:
> 1. The sum of the base rate of all leafs classes is 1Mbps.
> 2. Ethernet 10Mbits/sec NIC card is used.
> 3. At a given point in time, there is a lot of traffic in the network,
> and our node has only 0.7Mbits/sec available for transmission. The
> situation remains like this for a while.
> 4. During the same period, all flows are using completely their base
> rate (i.e. traffic is flowing in all classes at their base rate, so
> globally there is 1Mbps flowing in the queuing mechanism).
>
> Definitely, some classes will not get their base rate.
> And now, finally, here are my questions.
:)
> For both CBQ and HTB, which classes will start to starve first? Is this
> done according to their priority, according to their base rate, or is it
> totally random?
> Have HTB and CBQ been designed to handle this kind of situation?
>
> I am looking for answers in term of general behavior of HTB and CBQ.
Htb will handle this nicely. All traffic will distributed according to the
rates. I'm doing some tests about it, but someone gave me 30 vcd's with
StarTrek movies on it, so some of my tests are delayed :)
I did some tests about it but I have no results available. But the settings
like rate and burst are satisified even if there is less bandwidth available
then configured.
I think cbq does the same but I'm not sure.
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 prev parent reply other threads:[~2002-11-08 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-11-12 12:43 ` [LARTC] What happens when guaranteed BW cannot be delivered (HTB and Mathieu Deziel
2002-11-15 20:41 ` [LARTC] What happens when guaranteed BW cannot be delivered (HTB Mathieu Deziel
-- strict thread matches above, loose matches on Subject: below --
2002-11-12 16:15 [LARTC] What happens when guaranteed BW cannot be delivered (HTB and CBQ) 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-103679638205765@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.