From: patchwork-bot+netdevbpf@kernel.org <patchwork-bot+netdevbpf@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 net-next] ice, xsk: Move Rx allocation out of while-loop
Date: Tue, 15 Dec 2020 02:00:08 +0000 [thread overview]
Message-ID: <160799760821.15807.11906942397903153665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201211085410.59350-1-bjorn.topel@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 11 Dec 2020 09:54:10 +0100 you wrote:
> From: Bj?rn T?pel <bjorn.topel@intel.com>
>
> Instead doing the check for allocation in each loop, move it outside
> the while loop and do it every NAPI loop.
>
> This change boosts the xdpsock rxdrop scenario with 15% more
> packets-per-second.
>
> [...]
Here is the summary with links:
- [v2,net-next] ice, xsk: Move Rx allocation out of while-loop
https://git.kernel.org/netdev/net-next/c/5bb0c4b5eb61
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:[~2020-12-15 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 8:54 [Intel-wired-lan] [PATCH v2 net-next] ice, xsk: Move Rx allocation out of while-loop =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-12-15 2: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=160799760821.15807.11906942397903153665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=intel-wired-lan@osuosl.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