From: patchwork-bot+netdevbpf@kernel.org
To: Eyal Birger <eyal.birger@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, memxor@gmail.com,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
paul.chaignon@gmail.com, chen.dylane@linux.dev,
kpsingh@kernel.org, a.s.protopopov@gmail.com, yatsenko@meta.com,
ameryhung@gmail.com, tklauser@distanz.ch,
shmulik.ladkani@gmail.com, puranjay@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next,v2] bpf: clarify BPF_RB_NO_WAKEUP behavior for bpf_ringbuf_discard()
Date: Tue, 31 Mar 2026 22:50:06 +0000 [thread overview]
Message-ID: <177499740679.2977813.7335235373687761125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260331130612.3762433-1-eyal.birger@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 31 Mar 2026 06:06:12 -0700 you wrote:
> Clarify bpf_ringbuf_discard() documentation for BPF_RB_NO_WAKEUP.
>
> Discarded ring buffer records are still left in the ring buffer and are
> only skipped when user space consumes them. This can matter when
> BPF_RB_NO_WAKEUP is used: a later submit relying on adaptive wakeup
> might not wake the consumer, because the discarded record still needs to
> be consumed first.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: clarify BPF_RB_NO_WAKEUP behavior for bpf_ringbuf_discard()
https://git.kernel.org/bpf/bpf-next/c/f9a80c7ce49e
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:[~2026-03-31 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 13:06 [PATCH bpf-next,v2] bpf: clarify BPF_RB_NO_WAKEUP behavior for bpf_ringbuf_discard() Eyal Birger
2026-03-31 22:50 ` 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=177499740679.2977813.7335235373687761125.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=eyal.birger@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=paul.chaignon@gmail.com \
--cc=puranjay@kernel.org \
--cc=shmulik.ladkani@gmail.com \
--cc=song@kernel.org \
--cc=tklauser@distanz.ch \
--cc=yatsenko@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox