From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
benishay@nvidia.com, gal@nvidia.com, gmj@meta.com,
khalidm@nvidia.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, saeedm@nvidia.com, stable@vger.kernel.org
Subject: Re: [PATCH net V3 RESEND] net/mlx5e: do not HW-GRO coalesce small frames
Date: Tue, 18 Aug 2026 17:38:15 +0000 [thread overview]
Message-ID: <178707469522.2194892.9488420568567548375.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260816064259.3279548-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 16 Aug 2026 09:42:59 +0300 you wrote:
> From: Glenn Judd <gmj@meta.com>
>
> When hardware GRO (SHAMPO) coalesces a small IPv4/TCP segment that was
> padded up to the 60-byte minimum Ethernet frame, the trailing padding is
> folded into the merged payload causing padding to be delivered
> to the user as payload.
>
> [...]
Here is the summary with links:
- [net,V3,RESEND] net/mlx5e: do not HW-GRO coalesce small frames
https://git.kernel.org/netdev/net/c/e2466392a0b8
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-08-18 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 6:42 [PATCH net V3 RESEND] net/mlx5e: do not HW-GRO coalesce small frames Tariq Toukan
2026-08-18 17:38 ` 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=178707469522.2194892.9488420568567548375.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=benishay@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=gmj@meta.com \
--cc=khalidm@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=tariqt@nvidia.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