From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: quantum vs. burst
Date: Thu, 16 Jan 2003 17:56:41 +0000 [thread overview]
Message-ID: <marc-lartc-104273985508327@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104272413214891@msgid-missing>
On Thursday 16 January 2003 14:34, Pavel Mores wrote:
> Hello,
>
> a quick question: what exactly is the difference between quantum and
> burst in HTB?
>
> Original HTB documentation states the following with respect to
> quantums:
>
> "... when more classes want to borrow bandwidth they are each given some
> number of bytes before serving other competing class. This number is
> called quantum."
>
> Burst is defined like this:
>
> "The burst and cburst parameters control the amount of data that can be
> sent at the maximum (hardware) speed without trying to serve another
> class."
>
>
> From the quotes, the purpose of quantums and both burst parameters seem
> to be somewhat related, one might say overlapping. Is it that quantums
> apply in different situations than bursts? If so, when is each of
> quantum, burst and cburst applicable?
Quantum and bursts have nothing common. Quantum is used to share remaining
bandwidth between child classes. So each class can send "quantum" bytes.
Each class is controlled with 2 buckets, one for the rate, one for the ceil.
These buckets have also a burst and this is burst for rate and cburst for
ceil.
Very simplified situation as example : So even if you have a big quantum of
let's say 60.000 bytes and you have a ceil of 6.000 bytes/s, you can only
send 6.000 packets / second so it takes 10 seconds to send. But if you have
a burst of 30.000 byts/s and you have a very fast connection, you can send
30.000 bytes very fast, but the remaining packets are send at ceil speed so
6.000 bytes/s. So it will take 5 seconds to send all the data.
Some more info abot quantum can be found on www.docum.org on the faq page.
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:[~2003-01-16 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 13:34 [LARTC] HTB: quantum vs. burst Pavel Mores
2003-01-16 17:56 ` Stef Coene [this message]
2003-01-16 18:50 ` Pavel Mores
2003-01-16 19:05 ` Stef Coene
2003-01-16 19:48 ` Pavel Mores
2003-01-16 20:28 ` Stef Coene
2003-01-17 12:25 ` Pavel Mores
2003-01-18 14:20 ` 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-104273985508327@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox