Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Julián Muñoz" <jmunoz@telefonica.net>
To: lartc@vger.kernel.org
Subject: About burst and cburst in htb (Re: [LARTC] htb faq)
Date: Mon, 27 May 2002 13:01:11 +0000	[thread overview]
Message-ID: <marc-lartc-102250455414620@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102249699809502@msgid-missing>


On Mon, 27 May 2002, Martin Devera wrote:

> > > rate has burst
> > > ceil has cburst

> > So it means that when traffic is borrowed cburst is used, else burst ?
>
> Hmm .. do you understand the difference between ceil & rate ?

Yes, rate is the guaranteed bandwitdh, ceil is the maximum bandwidth.


> Everytime when ceil is computed then cburst is used and vice versa ..

I will try to answer to myself:


          ---------
          |       |
          |       |
   --------       ---------------------


Say you have a burst like this. When transmiting all the available
bandwitdh is used by the burst.

At the next oportunity, htb will ask himself:
its my turn, how long must be this burst ?

If the computed bandwidth used by this class is over "rate" (but less than
"ceil", the length will be "cburst". Else it will be "burst").

Is it this ??


-- 

      __o
    _ \<_
   (_)/(_)

Saludos de Julián
EA4ACL
-.-

Foro Wireless Madrid
http://opennetworks.rg3.net


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-05-27 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 10:55 About burst and cburst in htb (Re: [LARTC] htb faq) Julián Muñoz
2002-05-27 13:01 ` Julián Muñoz [this message]
2002-05-27 13:37 ` Martin Devera
2002-05-27 17:55 ` Julián Muñoz
2002-05-27 18:50 ` Martin Devera

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-102250455414620@msgid-missing \
    --to=jmunoz@telefonica.net \
    --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