CoDel AQM discussions
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] fq_"codel" in apple's gear
Date: Sat, 14 Oct 2023 21:17:28 +0300	[thread overview]
Message-ID: <3E02B7F5-D0C6-4C33-AFA9-30A2E54B155F@gmail.com> (raw)
In-Reply-To: <CAA93jw7+3nAiNieOFaeUhojYHPE3q33mhrN3zvdbJRePxzRzWA@mail.gmail.com>

> On 14 Oct, 2023, at 8:23 pm, Dave Taht <dave.taht@gmail.com> wrote:
> 
> I would really like someone with a fresh set of eyeballs to review the
> "codel"  portion of apple's latest code drop here:
> 
> https://www.linkedin.com/feed/update/urn:li:activity:7118969694987935744/

So far as I can tell, it still implements DRR++ (with a comment referencing RFC-8290), but not Codel (there's also no comment referencing RFC-8289).  There's at least one function for handling ECN which is simply not called, at least not in that source file.

In fact, I looked in the header to see where an ECN mark counter was defined.  It is referenced in essentially three places:  the definition, an extraction for reporting to userspace, and an increment - in a function implementing L4S marking, not Codel.

A similar counter for "early dropped" packets is incremented only when packets have to be dropped in an emergency because the queue is *full*.  That's the other counter I would expect to be touched by an AQM implementation.

So, no tangible improvement that I can find easily.

 - Jonathan Morton

  reply	other threads:[~2023-10-14 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14 17:23 Dave Taht
2023-10-14 18:17 ` Jonathan Morton [this message]
2023-10-14 18:50   ` Dave Taht
2023-10-14 19:01     ` Dave Taht
2023-10-14 19:44       ` Sebastian Moeller
2023-10-14 19:46         ` Dave Taht
2023-10-15 13:09           ` Sebastian Moeller

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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=3E02B7F5-D0C6-4C33-AFA9-30A2E54B155F@gmail.com \
    --to=chromatix99@gmail.com \
    --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