From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Cake] l4s kernel submission
Date: Thu, 14 Oct 2021 22:31:09 +0200 [thread overview]
Message-ID: <CBBD435B-5A6F-408D-B17C-B28F326B49AC@gmx.de> (raw)
In-Reply-To: <CAA93jw43C7CB-4Jv7h9NvvzjROdO5p2rVbPSZnmSJf0JAaCyaQ@mail.gmail.com>
Which does not change the inconvenient fact that L4S does not work over the open internet. But I bet that fq_codel with a shaper is going to be hands down the better L4S AQM compared to DualQ... (thanks to its fq nature it can forego the whole "coupling" heuristic mess and side-step the whole massive unfairness issues, and keeping the known working codel law for non-ECT(1) traffic also compared to dualq's burts intolerabt PIE variant also seems like a step in the right direction).
Then again it seems consequent given that the BBRv2 team seem to be on-board the L4S train; to put a somewhat positive spin (lipstick?) on this, I assume that the quality of the L4S engineering might improve...
Regards
Sebastian
P.S.: Witnessing the L4S drama in the IETF makes me appreciate how comparatively clean and elegant sausages are made...
> On Oct 14, 2021, at 22:06, Dave Taht <dave.taht@gmail.com> wrote:
>
> https://lore.kernel.org/all/20211014175918.60188-3-eric.dumazet@gmail.com/
>
> --
> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2021-10-14 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 20:06 Dave Taht
2021-10-14 20:31 ` Sebastian Moeller [this message]
2021-10-14 21:27 ` Dave Taht
2021-10-14 21:44 ` [Cake] [Ecn-sane] " Toke Høiland-Jørgensen
2021-10-14 22:00 ` Dave Taht
2021-10-14 22:10 ` Toke Høiland-Jørgensen
2021-10-14 22:17 ` Dave Taht
2021-10-16 8:04 ` Jonathan Morton
2021-10-16 8:38 ` Sebastian Moeller
2021-10-16 8:54 ` Jonathan Morton
2021-10-16 10:29 ` Sebastian Moeller
2021-10-16 12:49 ` Sebastian Moeller
2021-10-16 16:58 ` Rodney W. Grimes
2021-10-16 21:01 ` Dave Taht
2021-10-16 23:57 ` Michael Richardson
2021-10-18 13:02 ` Toke Høiland-Jørgensen
2021-10-19 2:45 ` Dave Taht
2021-10-19 11:19 ` Toke Høiland-Jørgensen
2021-10-19 13:30 ` Dave Taht
2021-10-19 13:34 ` Sebastian Moeller
2021-10-19 14:16 ` 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=CBBD435B-5A6F-408D-B17C-B28F326B49AC@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@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