From: Christian Hammers <ch@westend.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] definition of burst
Date: Tue, 30 Jul 2002 10:37:57 +0000 [thread overview]
Message-ID: <marc-lartc-102802557105491@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102802503804967@msgid-missing>
Hi
On Tue, Jul 30, 2002 at 01:28:56PM +0300, Anton Yurchenko wrote:
> How does HTB define burst. What does it consider a burst, I mean how
> does it destinguish when to allow traffic above rate(ceil), within
> burst(cburst) values?
From just reading the docs (not the actual source) I would say that
"rate" is only the rate in which the bucket is filled with tokens.
"burst" defines the size of the bucket. I.e. when the bucket is filled up
after a pause, you can send out as much packets as the bucket is large as
fast as you want. The burst therefore starts at a sometimes undefined point
in time but definetly ends when the bucket is simple empty. Because then,
the packets have to wait for new tokens which only arrives at the "rate"
frequency.
So "burst" defines the endurance of the burst.
(if you want those small-burst-until-the-bucket-is-empty to be not as fast
as possible but shaped as well then you have to use the maxpeak parameter.
HTH,
-christian-
--
Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0
ch@westend.com Internet & Security for Professionals Fax 0241/911879
WESTEND ist CISCO Systems Partner - Authorized Reseller
_______________________________________________
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-07-30 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 10:28 [LARTC] definition of burst Anton Yurchenko
2002-07-30 10:37 ` Christian Hammers [this message]
2002-07-30 11:00 ` Anton Yurchenko
2002-07-30 11:31 ` Christian Hammers
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-102802557105491@msgid-missing \
--to=ch@westend.com \
--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.