Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	Cake List <cake@lists.bufferbloat.net>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Cake] l4s kernel submission
Date: Fri, 15 Oct 2021 00:10:20 +0200	[thread overview]
Message-ID: <87pms71cmr.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw43kC8a4_8YL3dobgvpkLO5UPbOm8yeFvwhh0dgV9eiuw@mail.gmail.com>

Dave Taht <dave.taht@gmail.com> writes:

> On Thu, Oct 14, 2021 at 2:44 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> Dave Taht <dave.taht@gmail.com> writes:
>>
>> > weirdly enough, my gmail account has not received anything from netdev
>> > since oct 11.
>>
>> You're not alone in that:
>> https://lore.kernel.org/netdev/20211014112718.6aed7f47@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com/T/#t
>
> ok. One of these years I'll go back to running my own email server
> full time.

You can also subscribe to Linux lists by importing the mails from Lore,
as one of the replies in the thread above pointed out. Been meaning to
switch to that myself, but haven't gotten around to it yet...

>> > yes, i think fq_codel will be better, and even the proposed
>> > too-shallow threshold will make for less of a dent on the internet.
>> >
>> > still... I do wish I'd seen this earlier.
>>
>> Earlier? You forwarded the patch hours after it was posted...
>
> I have a daily search for fq_codel, bufferbloat, etc. I have noticed
> lately that some mailing list traffic from us is being indexed again.
> I wish I knew why our lists were not indexed by google.
>
> Anyway, lacking being on that thread, it's currently impossible to
> reply.

The Lore page contains instructions for various ways of replying even
without having the original email message in your mailbox. It's at the
bottom... 

> That said, the l4s fq_codel patch is intrinsically fair, which is
> vastly superior to the dualpi approach.

Yup, I agree it's better, but I don't like baking in the ECT(1)
semantics to UAPI. I suggested a filter-based approach which I'm
currently discussing with Eric on that thread as you might have noticed :)

-Toke

  reply	other threads:[~2021-10-14 22:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 20:06 [Ecn-sane] " Dave Taht
2021-10-14 20:31 ` [Ecn-sane] [Cake] " Sebastian Moeller
2021-10-14 21:27   ` Dave Taht
2021-10-14 21:44     ` Toke Høiland-Jørgensen
2021-10-14 22:00       ` Dave Taht
2021-10-14 22:10         ` Toke Høiland-Jørgensen [this message]
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-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/ecn-sane.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=87pms71cmr.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ecn-sane@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