All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Token Bucket: how does it really work?
Date: Thu, 23 Jan 2003 18:43:08 +0000	[thread overview]
Message-ID: <marc-lartc-104334949420291@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104333981615588@msgid-missing>

On Thursday 23 January 2003 17:34, kpeter wrote:
> Hello!
>
> I would like to know, how  the Token Bucket filter really works.
>
> An example:
>  r = 10 Kbyte/sec
>  b = 10 Kbyte
Do you mean burst ?

> I send 0.5 sec with 5 Kbyte/sec (A-> 2,5 Kbyte) and
> 0.5 sec with 15 Kbyte/sec (B-> 7,5 Kbyte), and
> 0.5 sec with 10 Kbyte/sec (C-> 5 Kbyte)
> after each other: ABCABCABC... and it goes through the tbf.
>
> What will happen?
>  1. All A phase will be sent from the tbf with 5 Kbyte/sec,
>      all B phase with 15 Kbyte/sec, and all C phase with 10 Kbyte/sec
>      without delay. => The sending rate really change and exceed the
>     average rate (10Kbyte/sec) by the B phases.
>  2.  0.0 : sending begins
>       0.5 : first A phase sent
>       1.0 : first 5Kbyte sent from B
>       1.25: remained 2,5 Kbyte sent from B
>       1.75: first C phase sent
>       2.0: second A phase sent
>        and so on => B and C was delayed, but sent continuously
>  3.  0.0 : sending begins
>       0.5 : first A phase sent
>       1.0 : first 5 Kbyte sent from B
>       1.5:  first C phase sent
>       1.75:second A phase sent
>        2.0: remained 2,5 Kbyte sent from B
>        and so on  -> here I mean that the traffic,
>        which couldn't be sent in time, will be sent
>        only then, when there is enough bandwidth
>        for it => B was delayed and cutted in two
>        parts, but A and C was sent in time.
> Which is the valid case? If none of them, than how
> would it happen?
> If the first case is valid, what does happen in the case
> of more tbf  and all of them wants to exceed the average
> rate, but the sum of the rates would be more than the
> availablebandwidth?
> Or it can't happen, because at an admission control
> for the tbf would be reserved a peak rate (like everybody
> want to send in the same time with peak rate), and if
> there is no more place for a next tbf, it would be
> rejected?
> (How is tbf implemented? Where can I find it?)
>
> I hope I was clear, if not please ask back!
I did some tests with htb.  It's based on tbf.  
But I'm not sure about your question.  Do you want to know how tbf delay 
packets or are you interested in the burst you can have?

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/

      reply	other threads:[~2003-01-23 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 16:34 [LARTC] Token Bucket: how does it really work? kpeter
2003-01-23 18:43 ` Stef Coene [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-104334949420291@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 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.