Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Cake List" <cake@lists.bufferbloat.net>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Cake] [Ecn-sane]  l4s kernel submission
Date: Tue, 19 Oct 2021 15:34:49 +0200	[thread overview]
Message-ID: <A7E9FA52-E02A-46B8-A518-B47778E23F8C@gmx.de> (raw)
In-Reply-To: <CAA93jw7zPCJE13DxB6QzM4eMh+-DkRaX-_XJhzAU5y9b9JbJbg@mail.gmail.com>

So that still leaves us with GSO introducing CE "spikes" into the network, that might not necessarily reflect what would happened if the meta-packet had been segmented before.... I note that rfc3168 probably will not care, since it will signal a CE mark for >= a full RTT anyway, but HFCCs will care. 

Regards
	Sebastian



> On Oct 19, 2021, at 15:30, Dave Taht <dave.taht@gmail.com> wrote:
> 
> On Tue, Oct 19, 2021 at 4:19 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> 
>> Dave Taht <dave.taht@gmail.com> writes:
>> 
>>> my more specific question was gro. On gro assembly is the dscp/ecn
>>> header examined?
>> 
>> Yes, and only packets with the same value get aggregated:
>> https://elixir.bootlin.com/linux/latest/source/net/ipv6/ip6_offload.c#L263
> 
> Good to know. Thx.
> 
>> -Toke
> 
> 
> 
> -- 
> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
> 
> Dave Täht CEO, TekLibre, LLC


  reply	other threads:[~2021-10-19 13:34 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
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 [this message]
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=A7E9FA52-E02A-46B8-A518-B47778E23F8C@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ecn-sane@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