From: patchwork-bot+netdevbpf@kernel.org
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
netdev@vger.kernel.org, magnus.karlsson@intel.com,
alexandr.lobakin@intel.com
Subject: Re: [PATCH v5 bpf-next 0/8] xsk: Intel driver improvements
Date: Thu, 27 Jan 2022 16:40:11 +0000 [thread overview]
Message-ID: <164330161156.2559.11459056156013759056.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220125160446.78976-1-maciej.fijalkowski@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 25 Jan 2022 17:04:38 +0100 you wrote:
> Hi,
>
> Unfortunately, similar scalability issues that were addressed for XDP
> processing in ice, exist for XDP in the zero-copy driver used by AF_XDP.
> Let's resolve them in mostly the same way as we did in [0] and utilize
> the Tx batching API from XSK buffer pool.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/8] ice: remove likely for napi_complete_done
https://git.kernel.org/bpf/bpf-next/c/a4e186693cbe
- [bpf-next,v5,2/8] ice: xsk: force rings to be sized to power of 2
https://git.kernel.org/bpf/bpf-next/c/296f13ff3854
- [bpf-next,v5,3/8] ice: xsk: handle SW XDP ring wrap and bump tail more often
https://git.kernel.org/bpf/bpf-next/c/3876ff525de7
- [bpf-next,v5,4/8] ice: make Tx threshold dependent on ring length
https://git.kernel.org/bpf/bpf-next/c/3dd411efe1ed
- [bpf-next,v5,5/8] i40e: xsk: move tmp desc array from driver to pool
https://git.kernel.org/bpf/bpf-next/c/d1bc532e99be
- [bpf-next,v5,6/8] ice: xsk: avoid potential dead AF_XDP Tx processing
https://git.kernel.org/bpf/bpf-next/c/86e3f78c8d32
- [bpf-next,v5,7/8] ice: xsk: improve AF_XDP ZC Tx and use batching API
https://git.kernel.org/bpf/bpf-next/c/126cdfe1007a
- [bpf-next,v5,8/8] ice: xsk: borrow xdp_tx_active logic from i40e
https://git.kernel.org/bpf/bpf-next/c/59e92bfe4df7
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:[~2022-01-27 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 16:04 [PATCH v5 bpf-next 0/8] xsk: Intel driver improvements Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 1/8] ice: remove likely for napi_complete_done Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 2/8] ice: xsk: force rings to be sized to power of 2 Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 3/8] ice: xsk: handle SW XDP ring wrap and bump tail more often Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 4/8] ice: make Tx threshold dependent on ring length Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 5/8] i40e: xsk: move tmp desc array from driver to pool Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 6/8] ice: xsk: avoid potential dead AF_XDP Tx processing Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 7/8] ice: xsk: improve AF_XDP ZC Tx and use batching API Maciej Fijalkowski
2022-01-25 16:04 ` [PATCH bpf-next v5 8/8] ice: xsk: borrow xdp_tx_active logic from i40e Maciej Fijalkowski
2022-01-26 8:07 ` Magnus Karlsson
2022-01-27 16: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=164330161156.2559.11459056156013759056.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandr.lobakin@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=maciej.fijalkowski@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.