netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, michael.chan@broadcom.com, ap420073@gmail.com
Subject: Re: [PATCH net-next] eth: bnxt: use page pool for head frags
Date: Wed, 13 Nov 2024 05:00:36 +0000	[thread overview]
Message-ID: <173147403650.787328.13748437765054715783.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241109035119.3391864-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  8 Nov 2024 19:51:19 -0800 you wrote:
> Testing small size RPCs (300B-400B) on a large AMD system suggests
> that page pool recycling is very useful even for just the head frags.
> With this patch (and copy break disabled) I see a 30% performance
> improvement (82Gbps -> 106Gbps).
> 
> Convert bnxt from normal page frags to page pool frags for head buffers.
> 
> [...]

Here is the summary with links:
  - [net-next] eth: bnxt: use page pool for head frags
    https://git.kernel.org/netdev/net-next/c/7ed816be35ab

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-11-13  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09  3:51 [PATCH net-next] eth: bnxt: use page pool for head frags Jakub Kicinski
2024-11-11  6:48 ` Taehee Yoo
2024-11-11 18:53   ` Jakub Kicinski
2024-11-12  6:03     ` Taehee Yoo
2024-11-13  5:00 ` 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=173147403650.787328.13748437765054715783.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).