General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Rebecca Drucker's talk sounds like it exposes an addressable bloat issue in Ciscos
Date: Sun, 10 Jan 2021 08:59:40 +0100	[thread overview]
Message-ID: <3ffdcd41-ede1-c9c5-5624-4a54d3c8197b@unix-ag.uni-kl.de> (raw)
In-Reply-To: <E461AD79-A1C3-4052-9A07-075A332A0731@gmail.com>

Hi,

On 10.01.21 08:19, Jonathan Morton wrote:
>> On 10 Jan, 2021, at 7:39 am, Erik Auerswald <auerswal@unix-ag.uni-kl.de> wrote:
>>
>> In my experience, asking about token-bucket algorithm details is often
>> a sign for the asker to not see the forest for the trees.
>
> IMHO, token-bucket is an obsolete algorithm that should not be used.

This level of detail seems useful (use of a different class of algorithm
instead of implementation details for a given algorithm class).

> [...]
> Many token-bucket implementations further complicate this by having two nested token-buckets.

Those are the details I had in mind as not of general importance.
They may matter for specific circumstances, but probably not much
in the context of short TCP streams using BBR vs. bufferbloat.

> [...]

Thanks,
Erik
-- 
Thinking doesn't guarantee that we won't make mistakes. But not thinking
guarantees that we will.
                         -- Leslie Lamport

  reply	other threads:[~2021-01-10  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 23:01 David Collier-Brown
2021-01-10  5:39 ` Erik Auerswald
2021-01-10  7:19   ` Jonathan Morton
2021-01-10  7:59     ` Erik Auerswald [this message]
2021-01-10 13:21     ` Toke Høiland-Jørgensen
2021-01-12 12:31   ` David Collier-Brown
2021-01-10 14:25 ` David Collier-Brown

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ffdcd41-ede1-c9c5-5624-4a54d3c8197b@unix-ag.uni-kl.de \
    --to=auerswal@unix-ag.uni-kl.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /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