From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] tossing acks into the background queue
Date: Mon, 22 Nov 2021 23:17:38 -0800 [thread overview]
Message-ID: <CAA93jw61GaPrLNmZn+ZuaA59UUo7SSb0DSSSrLH7rVSRqj92Xw@mail.gmail.com> (raw)
In-Reply-To: <67BC6CC2-F088-4C0D-8433-A09F4AC452FE@gmx.de>
On Mon, Nov 22, 2021 at 11:07 PM Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi Dave,
>
>
> On 23 November 2021 06:03:03 CET, Dave Taht <dave.taht@gmail.com> wrote:
> >ages ago I'd (we'd? I really don't remember - forgive me if I've
> >forgotten who actually leaned in on it) written a basic ack-filter in
> >ebpf. this was before cake gained tc actions and my primary use for
> >the tech was for asymmetric connections, and before the good
> >ack-filter arrived, and I was (and remain) unfriendly to this level of
> >dpi.
> >
> >That said, on a symmetric connection, deprioritizing pure acks to the
> >5% background queue nd then turning the cake ack-filter loose on it
> >might actually work.
> >
> >Am I on drugs/is there any point?
>
> I think at leat when using multiple priority tins forward and reverse traffic should by default use the same tin (I can see non-standard situations that want differential treatment). The argument is that unlike earlier attempts at ingress shaping that tried to throttle reverse ACKs? cake/codel do proper 'hit the brakes' signalling via marking/dropping and we want that signal to reach the other end as quickly as possible, no?
My thought was basically an optional filter that steered all pure acks
(no matter the classification) into the background queue.
Non-pure-acks (sacks) essentially jump the background queue and signal
that loss earlier. The backlog of other acks in background get
delivered out of order, but purely out of order and discarded by the
reciever.
> Regards
> Sebastian
>
>
> >
> >
> >
> >--
> >I tried to build a better future, a few times:
> >https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
> >
> >Dave Täht CEO, TekLibre, LLC
> >_______________________________________________
> >Cake mailing list
> >Cake@lists.bufferbloat.net
> >https://lists.bufferbloat.net/listinfo/cake
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2021-11-23 7:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 5:03 Dave Taht
2021-11-23 7:07 ` Sebastian Moeller
2021-11-23 7:17 ` Dave Taht [this message]
2021-11-23 7:32 ` Dave Taht
2021-11-23 7:33 ` Dave Taht
2021-11-23 8:06 ` Sebastian Moeller
2021-11-23 8:27 ` Dave Taht
2021-11-23 9:03 ` Sebastian Moeller
2021-11-23 10:39 ` Toke Høiland-Jørgensen
2021-11-23 11:31 ` Sebastian Moeller
2021-11-23 12:12 ` Toke Høiland-Jørgensen
2021-11-23 15:12 ` Dave Taht
2021-11-23 15:49 ` Toke Høiland-Jørgensen
2021-11-23 7:35 ` 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/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=CAA93jw61GaPrLNmZn+ZuaA59UUo7SSb0DSSSrLH7rVSRqj92Xw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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