From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Sebastian Moeller <moeller0@gmx.de>,
Cake List <cake@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Cake] [Ecn-sane] l4s kernel submission
Date: Mon, 18 Oct 2021 19:45:44 -0700 [thread overview]
Message-ID: <CAA93jw52-6oaOgDCS7m8+zF0VDFDEgADat=So7zWPTwNrR988w@mail.gmail.com> (raw)
In-Reply-To: <878ryqjxke.fsf@toke.dk>
my more specific question was gro. On gro assembly is the dscp/ecn
header examined?
On Mon, Oct 18, 2021 at 6:02 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Dave Taht <dave.taht@gmail.com> writes:
>
> > An open question for me:
> >
> > What happens when a GSO packet is marked? Do all the packets get the
> > marking, or just the first?
>
> When segmenting a GSO packet, the IP header is copied to all segments.
> The code has grown quite complex over the years, but it's easier to see
> in the original submission from 2006:
>
> https://lore.kernel.org/all/20060622081400.GC22671@gondor.apana.org.au/
>
> Which means all packets in a GSO segment will end up marked on the
> wire...
>
> -Toke
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2021-10-19 2:45 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 [this message]
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='CAA93jw52-6oaOgDCS7m8+zF0VDFDEgADat=So7zWPTwNrR988w@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