From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake's ack-filter vs GSO
Date: Fri, 23 Feb 2024 11:26:58 -0500 [thread overview]
Message-ID: <CAA93jw7y+S6NvRf+Q_VtqJkDnWQJO5Cr5d_En6wHvas6pEBT1w@mail.gmail.com> (raw)
In-Reply-To: <875xyldhbk.fsf@toke.dk>
On Sun, Feb 18, 2024 at 8:37 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Dave Taht via Cake <cake@lists.bufferbloat.net> writes:
>
> > It has been years since I looked at cake's code.
> >
> > Does anyone remember why we do not ack-filter a gso-split?
>
> Because a GSO packet cannot be a pure ACK, so it wouldn't be filtered
> anyway...
But a GRO packet can, and most likely IS a pure ack packet train that
could and should be thinned. I think. Yes?
Anyway, I put in for a small grant a few months ago with NLNET on this
(and keep hoping that somewhere out there, there are more orgs using
cake willing to throw in? I mean there are hundreds now! Can anyone
reach out to them?)
It might be approved in a month or so - but it also had scope in
looking at transports and the BSDs, and I keep hoping to somehow find
enough resources to have a project with 3 core folk running at it part
time for 2 years.
https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit
Elsewhere a volunteer started some work on validating the fq_codel
implementations of openbsd and freebsd. The results are interesting!
The "wrong" openbsd version with a 400 count cap does not behave much
differently from the one with the pure newton invsqrt approximation in
the tests so far. Can anyone suggest tests to exercise it?
Do I have the energy to write them up yet? No. I might start yet
another mailing list to discuss it. My long term hope is to gain
enough experience, somehow get cake ported over to those OSes
eventually, but I would settle for just quieting the noise in the
opnsense world.
I am trying to have a BQL discussion on the netdev list also, about
virtio-net...
Maybe this presentation will gain traction:
https://www.youtube.com/watch?v=rWnb543Sdk8&t=2603s
>
> -Toke
--
https://blog.cerowrt.org/post/2024_predictions/
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2024-02-23 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 0:01 Dave Taht
2024-02-18 0:31 ` Jonathan Morton
2024-02-18 13:37 ` Toke Høiland-Jørgensen
2024-02-23 16:26 ` Dave Taht [this message]
2024-02-23 16:39 ` Toke Høiland-Jørgensen
2024-02-23 17:03 ` Dave Taht
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7y+S6NvRf+Q_VtqJkDnWQJO5Cr5d_En6wHvas6pEBT1w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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