Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org,
	intel-wired-lan@lists.osuosl.org, bpf@vger.kernel.org,
	magnus.karlsson@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] i40e: read the XDP program once per NAPI
Date: Sat, 25 Jun 2022 05:40:14 +0000	[thread overview]
Message-ID: <165613561417.1389.16592018504137661188.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220623100852.7867-1-ciara.loftus@intel.com>

Hello:

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

On Thu, 23 Jun 2022 10:08:52 +0000 you wrote:
> Similar to how it's done in the ice driver since 'eb087cd82864 ("ice:
> propagate xdp_ring onto rx_ring")', read the XDP program once per NAPI
> instead of once per descriptor cleaned. I measured an improvement in
> throughput of 2% for the AF_XDP xdpsock l2fwd benchmark for zero copy mode
> and 1% for copy mode.
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> 
> [...]

Here is the summary with links:
  - [net-next,v2] i40e: read the XDP program once per NAPI
    https://git.kernel.org/netdev/net-next/c/78f319315764

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


_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2022-06-25  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 10:08 [Intel-wired-lan] [PATCH net-next v2] i40e: read the XDP program once per NAPI Ciara Loftus
2022-06-25  5:40 ` 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=165613561417.1389.16592018504137661188.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=ciara.loftus@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=magnus.karlsson@intel.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