All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: About burst and cburst in htb (Re: [LARTC] htb faq)
Date: Mon, 27 May 2002 13:37:09 +0000	[thread overview]
Message-ID: <marc-lartc-102250671316544@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102249699809502@msgid-missing>

> > 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 ??

---
Please don't be impatient !
I didn't respond to your mail instantly and you sent me it again.
---

I don't think so. The burst values are used by htb to answer
question "is the class over rate" and "is the class over ceil".
The rate and ceil estimator is coupled by pairs rate/burst and
ceil/cburst. It is by definition of leaky bucket.

So that by raising burst you higher probability that next question
whether the class is under its rate will be answered "yes".

devik

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

  parent reply	other threads:[~2002-05-27 13:37 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
2002-05-27 13:37 ` Martin Devera [this message]
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-102250671316544@msgid-missing \
    --to=devik@cdi.cz \
    --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.