From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Bloat] [Codel] fq_"codel" in apple's gear
Date: Sat, 14 Oct 2023 12:01:18 -0700 [thread overview]
Message-ID: <CAA93jw5uJYhzuYD0Mgb=MtvCosZwkEb1m4jM0tFHw=87W1XHpg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5VcHe0dpSVFu9zXd58JUhNiA1Z=gVASohfHctHTC+EpA@mail.gmail.com>
I would be curious if fq_"codel" was still in use on the current apple
products. On an OSX box, the magic command to look at the stats was:
netstat -I en0 -qq # or whatever the right interface is
And you can just poll that while slamming traffic through it.
On Sat, Oct 14, 2023 at 11:50 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> On Sat, Oct 14, 2023 at 11:17 AM Jonathan Morton <chromatix99@gmail.com> wrote:
> >
> > > 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.
>
> Thank you for summoning the gumption to look again. I was having blood
> pressure problems.
>
> > 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.
>
> Yep. I had run some tests then and saw the rtts climbing alarmingly,
> while polling their stack and only seeing drops in big bursty batches,
> total resets of the tcp flow, and so on.
>
> > So, no tangible improvement that I can find easily.
> >
> > - Jonathan Morton
>
>
>
> --
> Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
> Dave Täht CSO, LibreQos
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
next parent reply other threads:[~2023-10-14 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw7+3nAiNieOFaeUhojYHPE3q33mhrN3zvdbJRePxzRzWA@mail.gmail.com>
[not found] ` <3E02B7F5-D0C6-4C33-AFA9-30A2E54B155F@gmail.com>
[not found] ` <CAA93jw5VcHe0dpSVFu9zXd58JUhNiA1Z=gVASohfHctHTC+EpA@mail.gmail.com>
2023-10-14 19:01 ` Dave Taht [this message]
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/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='CAA93jw5uJYhzuYD0Mgb=MtvCosZwkEb1m4jM0tFHw=87W1XHpg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
/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