From: patchwork-bot+netdevbpf@kernel.org
To: Magnus Karlsson <magnus.karlsson@gmail.com>
Cc: magnus.karlsson@intel.com, bjorn.topel@intel.com, ast@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org,
jonathan.lemon@gmail.com, kuba@kernel.org,
john.fastabend@gmail.com, bpf@vger.kernel.org,
jeffrey.t.kirsher@intel.com, anthony.l.nguyen@intel.com,
maciej.fijalkowski@intel.com, maciejromanfijalkowski@gmail.com,
intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH bpf-next v3 0/5] xsk: i40e: Tx performance improvements
Date: Tue, 17 Nov 2020 21:20:06 +0000 [thread overview]
Message-ID: <160564800642.24253.1580711036123652762.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1605525167-14450-1-git-send-email-magnus.karlsson@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 16 Nov 2020 12:12:42 +0100 you wrote:
> This patch set improves the performance of mainly the Tx processing of
> AF_XDP sockets. Though, patch 3 also improves the Rx path. All in all,
> this patch set improves the throughput of the l2fwd xdpsock
> application by around 11%. If we just take a look at Tx processing part,
> it is improved by 35% to 40%.
>
> Hopefully the new batched Tx interfaces should be of value to other
> drivers implementing AF_XDP zero-copy support. But patch #3 is generic
> and will improve performance of all drivers when using AF_XDP sockets
> (under the premises explained in that patch).
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/5] samples/bpf: increment Tx stats at sending
https://git.kernel.org/bpf/bpf-next/c/90da4b3208d3
- [bpf-next,v3,2/5] i40e: remove unnecessary sw_ring access from xsk Tx
https://git.kernel.org/bpf/bpf-next/c/f320460b9489
- [bpf-next,v3,3/5] xsk: introduce padding between more ring pointers
https://git.kernel.org/bpf/bpf-next/c/b8c7aece29bc
- [bpf-next,v3,4/5] xsk: introduce batched Tx descriptor interfaces
https://git.kernel.org/bpf/bpf-next/c/9349eb3a9d2a
- [bpf-next,v3,5/5] i40e: use batched xsk Tx interfaces to increase performance
https://git.kernel.org/bpf/bpf-next/c/3106c580fb7c
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-11-17 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 11:12 [PATCH bpf-next v3 0/5] xsk: i40e: Tx performance improvements Magnus Karlsson
2020-11-16 11:12 ` [PATCH bpf-next v3 1/5] samples/bpf: increment Tx stats at sending Magnus Karlsson
2020-11-16 11:12 ` [PATCH bpf-next v3 2/5] i40e: remove unnecessary sw_ring access from xsk Tx Magnus Karlsson
2020-11-16 11:12 ` [PATCH bpf-next v3 3/5] xsk: introduce padding between more ring pointers Magnus Karlsson
2020-11-16 11:12 ` [PATCH bpf-next v3 4/5] xsk: introduce batched Tx descriptor interfaces Magnus Karlsson
2020-11-17 19:07 ` John Fastabend
2020-11-17 19:36 ` Magnus Karlsson
2020-11-16 11:12 ` [PATCH bpf-next v3 5/5] i40e: use batched xsk Tx interfaces to increase performance Magnus Karlsson
2020-11-17 21:20 ` 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=160564800642.24253.1580711036123652762.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=maciejromanfijalkowski@gmail.com \
--cc=magnus.karlsson@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).