From: Felix Fietkau <nbd@nbd.name>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
David Ahern <dsahern@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] net: add TCP fraglist GRO support
Date: Wed, 24 Apr 2024 18:26:37 +0200 [thread overview]
Message-ID: <4e5704f4-f715-4e39-876b-ea5d8a83a0a3@nbd.name> (raw)
In-Reply-To: <6629177f6b4c7_1a76072949b@willemb.c.googlers.com.notmuch>
On 24.04.24 16:30, Willem de Bruijn wrote:
>> > If keeping, this refinement can probably a separate follow-on patch in
>> > the series too:
>> >
>> > - refactor existing udp code
>> > - add segmentation support to handle such packets on tx
>> > - add coalescing support that starts building such packets on rx
>> > - refine coalescing choice
>> I don't really understand what you're suggesting. With my patch, the GRO
>> code handles coalescing of packets. Segmentation on output is also
>> supported. The next version of my patch will fix the cases that were too
>> similar to the UDP code, so I guess refactoring to share code doesn't
>> really make sense there.
>> Am I missing something?
>
> I mean if breaking up into a series. First have the refactoring patch
> which should be easy to review to be a noop. Then add the segmentation
> code, which needs to exist before packets may arrive that depend on
> it. Then add the code that produces such packets. To break up into
> manageable chunks.
Right, that makes sense.
Thanks,
- Felix
next prev parent reply other threads:[~2024-04-24 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 9:41 [RFC] net: add TCP fraglist GRO support Felix Fietkau
2024-04-23 10:15 ` Eric Dumazet
2024-04-23 10:25 ` Felix Fietkau
2024-04-23 11:17 ` Eric Dumazet
2024-04-23 11:55 ` Felix Fietkau
2024-04-23 12:11 ` Eric Dumazet
2024-04-23 12:23 ` Felix Fietkau
2024-04-23 13:07 ` Eric Dumazet
2024-04-23 14:34 ` Paolo Abeni
2024-04-23 16:55 ` Felix Fietkau
2024-04-24 1:24 ` Willem de Bruijn
2024-04-24 13:50 ` Felix Fietkau
2024-04-24 14:30 ` Willem de Bruijn
2024-04-24 16:26 ` Felix Fietkau [this message]
2024-04-23 15:03 ` David Ahern
2024-04-23 15:18 ` Eric Dumazet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e5704f4-f715-4e39-876b-ea5d8a83a0a3@nbd.name \
--to=nbd@nbd.name \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.com \
/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