From: Alexey Talikov <alexey_talikov@texlab.com.uz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb faq
Date: Mon, 27 May 2002 09:58:56 +0000 [thread overview]
Message-ID: <marc-lartc-102249363907351@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102234668830768@msgid-missing>
See chapter 5 on http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm
The burst and cburst of a class should always be at least as high as that of any of it children
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 (cburst-ceil burst-rate)
i.e. class borrowed on rate it used burst on ceil it used cburst
It possible in this case when ancestor borrwed all traffic from his descendant and
ancestor of this ancestor borrowed all traffic from it
Any problem ???
27.05.2002 13:54:16, Julián Muñoz <jmunoz@telefonica.net> wrote:
>On Sun, 26 May 2002, Martin Devera wrote:
>
>> cburst is for ceil rate and burst is for normal rate.
>> or
>> rate has burst
>> ceil has cburst
>>
>> probably it is not clear from the manual ?
>
>No :-)
>
>So it means that when traffic is borrowed cburst is used, else burst ?
>
>
>
>--
>Saludos de Julián
>EA4ACL
>-.-
>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
-----------------------------------
mailto:alexey_talikov@texlab.com.uz
BR
Alexey Talikov
FORTEK
-----------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-27 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 17:10 [LARTC] htb faq Julián Muñoz
2002-05-26 10:13 ` Martin Devera
2002-05-27 8:54 ` Julián Muñoz
2002-05-27 9:51 ` Martin Devera
2002-05-27 9:58 ` Alexey Talikov [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-102249363907351@msgid-missing \
--to=alexey_talikov@texlab.com.uz \
--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.