General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>, codel@lists.bufferbloat.net
Subject: Re: [Bloat] [Codel] ACM queue article on facebook´s "Adaptive LIFO" and codel
Date: Tue, 11 Apr 2023 05:41:07 +0300	[thread overview]
Message-ID: <541FD0C8-4BAF-47D1-93F8-7C5A879ADF23@gmail.com> (raw)
In-Reply-To: <CAA93jw42m6wYHvy4rGOtpMyxCi4mJA6fFLmZ_BL1fvFSU=d5=A@mail.gmail.com>

> On 11 Apr, 2023, at 5:12 am, Dave Taht <dave.taht@gmail.com> wrote:
> 
> I have no idea what an "adaptive LIFO" is, but the acm queue paper
> here just takes the defaults from codel...
> 
> https://twitter.com/teivah/status/1645362443986640896

They're applying it to a server request queue, not a network packet queue.  I can see the logic of it in that context, but I would also note that LIFO breaks one of Codel's core assumptions, which is that the maximum delay of the queue it's controlling can be inferred from the delay experienced by the most recently dequeued item.

Maybe it still happens to work by accident, or maybe they've implemented some specific workaround, but that paper is a very high-level overview (of more than one technology, to boot) without much technical detail.  If I didn't already know a great deal about Codel from the coal face, I wouldn't even know to consider such a failure mode, let alone be able to infer what they could do to mitigate it.

 - Jonathan Morton

      reply	other threads:[~2023-04-11  2:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  2:12 [Bloat] " Dave Taht
2023-04-11  2:41 ` Jonathan Morton [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

  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=541FD0C8-4BAF-47D1-93F8-7C5A879ADF23@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@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