From: patchwork-bot+netdevbpf@kernel.org
To: Michael Baikov <manpacket@gmail.com>
Cc: ecree.xilinx@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-net-drivers@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: sfc: run all the packets through GRO
Date: Mon, 16 Nov 2026 23:20:08 +0000 [thread overview]
Message-ID: <179487120827.232553.3824112679910149273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109-sfc-udp-gro2-v1-1-025d385f007f@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 09 Nov 2026 13:08:35 -0500 you 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. Now, when
> GRO is enabled - pass all the messages though GRO subsystem.
> Tested on SFC9250 with a UDP_GRO socket.
>
> [...]
Here is the summary with links:
- net: sfc: run all the packets through GRO
https://git.kernel.org/netdev/net-next/c/2d1d687936cd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-16 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 18:08 [PATCH] net: sfc: run all the packets through GRO Michael Baikov
2026-11-09 18:08 ` Michael Baikov via B4 Relay
2026-11-12 2:02 ` netdev-bot+sashiko
2026-11-16 23:20 ` patchwork-bot+netdevbpf [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=179487120827.232553.3824112679910149273.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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 \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.