From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Cake] l4s kernel submission
Date: Tue, 19 Oct 2021 07:16:52 -0700 [thread overview]
Message-ID: <CAA93jw6_7LUWo4=JoXTuQm1OK1rQJpJHYjF0TcUWo3nsOQxdQQ@mail.gmail.com> (raw)
In-Reply-To: <A7E9FA52-E02A-46B8-A518-B47778E23F8C@gmx.de>
On Tue, Oct 19, 2021 at 6:34 AM Sebastian Moeller <moeller0@gmx.de> wrote:
>
> 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 am not sure the proper term for this, the "wavefront" of a GSO'd
packet will get scheduled and not marked, and the tail of the wave,
were it not GSO'd, might be marked. The next wavefront, assuming it's
accumulated a negative deficit, will all be marked. Now what this
means for the next "wavefront" I don't really understand, my guess is
packets will start to get paced naturally from the sender but might
still be arriving in a bunch to the receiver.
On the GRO side, I am glad toke has reassured me that at least in
linux, GRO checks all the headers. as for what hardware offloads or
the device drivers might do, unknown.
In our world we've been splitting up gro/gso in self defense so much
that we don't know what the rest of the world looks like. sch_fq has a
3000 byte quantum and always releases two packets by default.
> I note that rfc3168 probably will not care, since it will signal a CE mark for >= a full RTT anyway, but HFCCs will care.
I have long thought that responding better to multiple rfc3168 marks
in an RTT would be a nice addition for a transport to have. But, no,
they don't 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
>
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
prev parent reply other threads:[~2021-10-19 14:17 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
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 [this message]
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='CAA93jw6_7LUWo4=JoXTuQm1OK1rQJpJHYjF0TcUWo3nsOQxdQQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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