From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
"Cake List" <cake@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Cake] [Ecn-sane] l4s kernel submission
Date: Sat, 16 Oct 2021 11:54:59 +0300 [thread overview]
Message-ID: <C6AC65FB-9BBB-4FCE-8C9F-A270680617C1@gmail.com> (raw)
In-Reply-To: <1F8C74DF-1384-4F72-904A-8293369DE95D@gmx.de>
> On 16 Oct, 2021, at 11:38 am, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> I also think that some one subscribed should weight in on the exempt one packet from marking, especially in the light of GRO/GSO.
I do have some experience with this from Cake, but Cake has the distinct benefit of (usually) knowing what the dequeue rate is, without having to estimate it. Without that knowledge, I'm not sure it's profitable to guess - except to specifically avoid tail *loss*, which is not at all the same as *marking* the last packet.
- Jonathan Morton
next prev parent reply other threads:[~2021-10-16 8:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 20:06 [Cake] " Dave Taht
2021-10-14 20:31 ` Sebastian Moeller
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 [this message]
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=C6AC65FB-9BBB-4FCE-8C9F-A270680617C1@gmail.com \
--to=chromatix99@gmail.com \
--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