From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: daniel@iogearbox.net, john.fastabend@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
bjorn@kernel.org, ast@kernel.org, andrii@kernel.org,
edumazet@google.com, haoluo@google.com, hawk@kernel.org,
jolsa@kernel.org, jonathan.lemon@gmail.com, kpsingh@kernel.org,
maciej.fijalkowski@intel.com, magnus.karlsson@intel.com,
martin.lau@linux.dev, pabeni@redhat.com, song@kernel.org,
sdf@google.com, tglx@linutronix.de, yonghong.song@linux.dev,
toke@redhat.com
Subject: Re: [PATCH bpf-next -v5] net: Add a warning if NAPI cb missed xdp_do_flush().
Date: Tue, 17 Oct 2023 13:10:23 +0000 [thread overview]
Message-ID: <169754822344.726.6139633216361785104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231016125738.Yt79p1uF@linutronix.de>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 16 Oct 2023 14:57:38 +0200 you wrote:
> A few drivers were missing a xdp_do_flush() invocation after
> XDP_REDIRECT.
>
> Add three helper functions each for one of the per-CPU lists. Return
> true if the per-CPU list is non-empty and flush the list.
> Add xdp_do_check_flushed() which invokes each helper functions and
> creates a warning if one of the functions had a non-empty list.
> Hide everything behind CONFIG_DEBUG_NET.
>
> [...]
Here is the summary with links:
- [bpf-next,-v5] net: Add a warning if NAPI cb missed xdp_do_flush().
https://git.kernel.org/bpf/bpf-next/c/9a675ba55a96
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:[~2023-10-17 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 16:58 [PATCH bpf-next] net: Add a warning if NAPI cb missed xdp_do_flush() Sebastian Andrzej Siewior
2023-09-29 17:52 ` Toke Høiland-Jørgensen
2023-10-04 14:09 ` Jakub Kicinski
2023-10-06 15:49 ` [PATCH bpf-next v2] " Sebastian Andrzej Siewior
2023-10-06 17:21 ` kernel test robot
2023-10-06 19:31 ` Jakub Kicinski
2023-10-07 15:43 ` [PATCH bpf-next v3] " Sebastian Andrzej Siewior
2023-10-10 6:57 ` [PATCH bpf-next -v4] " Sebastian Andrzej Siewior
2023-10-11 4:42 ` John Fastabend
2023-10-16 11:56 ` Daniel Borkmann
2023-10-16 12:57 ` [PATCH bpf-next -v5] " Sebastian Andrzej Siewior
2023-10-17 13:10 ` patchwork-bot+netdevbpf [this message]
2023-10-08 13:48 ` [PATCH bpf-next v2] " Simon Horman
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=169754822344.726.6139633216361785104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jonathan.lemon@gmail.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=toke@redhat.com \
--cc=yonghong.song@linux.dev \
/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.