From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net, saeedm@nvidia.com,
leon@kernel.org, mbloch@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
gal@nvidia.com, moshe@nvidia.com, dtatulea@nvidia.com
Subject: Re: [PATCH net-next V2] net/mlx5e: SHAMPO, Switch to header memcpy
Date: Fri, 06 Feb 2026 02:50:08 +0000 [thread overview]
Message-ID: <177034620808.657894.1041994885546152344.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204200345.1724098-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Feb 2026 22:03:45 +0200 you wrote:
> From: Dragos Tatulea <dtatulea@nvidia.com>
>
> Previously the HW-GRO code was using a separate page_pool for the header
> buffer. The pages of the header buffer were replenished via UMR. This
> mechanism has some drawbacks:
> - Reference counting on the page_pool page frags is not cheap.
> - UMRs have HW overhead for updating and also for access. Especially for
> the KLM type which was previously used.
> - UMR code for headers is complex.
>
> [...]
Here is the summary with links:
- [net-next,V2] net/mlx5e: SHAMPO, Switch to header memcpy
https://git.kernel.org/netdev/net-next/c/24cf78c73831
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-02-06 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 20:03 [PATCH net-next V2] net/mlx5e: SHAMPO, Switch to header memcpy Tariq Toukan
2026-02-04 21:53 ` Jacob Keller
2026-02-06 2:50 ` 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=177034620808.657894.1041994885546152344.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@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=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--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