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, maximmi@nvidia.com, kuba@kernel.org,
bjorn@kernel.org
Subject: Re: [PATCH v2 bpf-next 00/14] xsk: stop NAPI Rx processing on full XSK RQ
Date: Fri, 15 Apr 2022 19:20:13 +0000 [thread overview]
Message-ID: <165005041371.20714.5228687866085513373.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220413153015.453864-1-maciej.fijalkowski@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 13 Apr 2022 17:30:01 +0200 you wrote:
> v2:
> - add likely for internal redirect return codes in ice and ixgbe
> (Jesper)
> - do not drop the buffer that head pointed to at full XSK RQ (Maxim)
> - terminate Rx loop only when need_wakeup feature is enabled (Maxim)
> - reword from 'stop softirq processing' to 'stop NAPI Rx processing'
> - s/ENXIO/EINVAL in mlx5 and stmmac's ndo_xsk_wakeup to keep it
> consitent with Intel's drivers (Maxim)
> - include Jesper's Acks
>
> [...]
Here is the summary with links:
- [v2,bpf-next,01/14] xsk: improve xdp_do_redirect() error codes
https://git.kernel.org/bpf/bpf-next/c/c6c1f11b691e
- [v2,bpf-next,02/14] xsk: diversify return codes in xsk_rcv_check()
https://git.kernel.org/bpf/bpf-next/c/2be4a677ccb2
- [v2,bpf-next,03/14] ice: xsk: decorate ICE_XDP_REDIR with likely()
https://git.kernel.org/bpf/bpf-next/c/0bd5ab511e30
- [v2,bpf-next,04/14] ixgbe: xsk: decorate IXGBE_XDP_REDIR with likely()
https://git.kernel.org/bpf/bpf-next/c/d090c885860f
- [v2,bpf-next,05/14] ice: xsk: terminate Rx side of NAPI when XSK Rx queue gets full
https://git.kernel.org/bpf/bpf-next/c/50ae06648073
- [v2,bpf-next,06/14] i40e: xsk: terminate Rx side of NAPI when XSK Rx queue gets full
https://git.kernel.org/bpf/bpf-next/c/b8aef650e549
- [v2,bpf-next,07/14] ixgbe: xsk: terminate Rx side of NAPI when XSK Rx queue gets full
https://git.kernel.org/bpf/bpf-next/c/c7dd09fd4628
- [v2,bpf-next,08/14] ice: xsk: diversify return values from xsk_wakeup call paths
https://git.kernel.org/bpf/bpf-next/c/ed8a6bc60f9e
- [v2,bpf-next,09/14] i40e: xsk: diversify return values from xsk_wakeup call paths
https://git.kernel.org/bpf/bpf-next/c/ed7ae2d62217
- [v2,bpf-next,10/14] ixgbe: xsk: diversify return values from xsk_wakeup call paths
https://git.kernel.org/bpf/bpf-next/c/0f8bf018899e
- [v2,bpf-next,11/14] mlx5: xsk: diversify return values from xsk_wakeup call paths
https://git.kernel.org/bpf/bpf-next/c/7b7f2f273d87
- [v2,bpf-next,12/14] stmmac: xsk: diversify return values from xsk_wakeup call paths
https://git.kernel.org/bpf/bpf-next/c/a817ead4154d
- [v2,bpf-next,13/14] ice: xsk: avoid refilling single Rx descriptors
https://git.kernel.org/bpf/bpf-next/c/4efad196163f
- [v2,bpf-next,14/14] xsk: drop ternary operator from xskq_cons_has_entries
https://git.kernel.org/bpf/bpf-next/c/0fb53aabc5fc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-04-15 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 15:30 [PATCH v2 bpf-next 00/14] xsk: stop NAPI Rx processing on full XSK RQ Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 01/14] xsk: improve xdp_do_redirect() error codes Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 02/14] xsk: diversify return codes in xsk_rcv_check() Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 03/14] ice: xsk: decorate ICE_XDP_REDIR with likely() Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 04/14] ixgbe: xsk: decorate IXGBE_XDP_REDIR " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 05/14] ice: xsk: terminate Rx side of NAPI when XSK Rx queue gets full Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 06/14] i40e: " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 07/14] ixgbe: " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 08/14] ice: xsk: diversify return values from xsk_wakeup call paths Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 09/14] i40e: " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 10/14] ixgbe: " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 11/14] mlx5: " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 12/14] stmmac: " Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 13/14] ice: xsk: avoid refilling single Rx descriptors Maciej Fijalkowski
2022-04-13 15:30 ` [PATCH v2 bpf-next 14/14] xsk: drop ternary operator from xskq_cons_has_entries Maciej Fijalkowski
2022-04-15 19:20 ` patchwork-bot+netdevbpf [this message]
2022-08-19 8:35 ` [PATCH v2 bpf-next 00/14] xsk: stop NAPI Rx processing on full XSK RQ Maxim Mikityanskiy
[not found] ` <f1eea2e9ca337e0c4e072bdd94a89859a4539c09.camel@nvidia.com>
2022-08-23 9:49 ` Maxim Mikityanskiy
2022-08-23 11:24 ` Maciej Fijalkowski
2022-08-23 13:46 ` Maxim Mikityanskiy
2022-08-24 5:18 ` John Fastabend
2022-08-25 14:42 ` Maxim Mikityanskiy
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=165005041371.20714.5228687866085513373.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandr.lobakin@intel.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=maximmi@nvidia.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).