From: Paolo Abeni <pabeni@redhat.com>
To: Edward Cree <ecree.xilinx@gmail.com>,
manpacket@gmail.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: sfc: run hardware-classified UDP packets through GRO
Date: Wed, 21 Oct 2026 13:32:34 +0200 [thread overview]
Message-ID: <bad72d8e-f424-4be7-8376-30ff0155e2d7@redhat.com> (raw)
In-Reply-To: <e6e5a292-0512-47d0-964b-249ff35074ac@gmail.com>
On 10/19/26 15:38, Edward Cree wrote:
> On 18/10/2026 22:05, Michael Baikov via B4 Relay wrote:
>> From: Michael Baikov <manpacket@gmail.com>
>>
>> This commit partially undoes changes made by the commit e79255de8581
>> ("sfc: Do not pass non-TCP packets into GRO code"). Those changes made
>> sense back then, but now GRO can help with more message types. Instead
>> of passing just TCP packets driver to GRO now also pass UDP packets.
>>
>> Tested on SFC9250 with a UDP_GRO socket.
>>
>> Signed-off-by: Michael Baikov <manpacket@gmail.com>
>
> This seems sensible enough, but I wonder whether, instead of doing GRO
> on TCP|UDP, it would be better at this point to just pass all protocols
> to GRO and not try to be clever about it in the driver. I don't know
> how likely other ipprotos are to grow GRO support in the future, or
> whether the front-end check in the driver (potentially adding cycles to
> every RX) is more expensive than having random IP go partway up the GRO
> stack to then be kicked out onto the non-GRO RX path, given that
> there's not likely to be much high-rate traffic that's neither TCP nor
> UDP (whereas when we wanted to separate those two there was potentially
> much more value in doing so early).
> So on those grounds I think there's a case for a straight revert of
> e79255de8581,
I also agree a clean revert would be the better option.
Please note we are in the merge window right now, you need to wait
until net-next re-opens for the new revision.
/P
prev parent reply other threads:[~2026-10-21 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 21:05 Michael Baikov via B4 Relay
2026-10-19 13:38 ` Edward Cree
2026-10-21 11:32 ` Paolo Abeni [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bad72d8e-f424-4be7-8376-30ff0155e2d7@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=manpacket@gmail.com \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®