From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org,
yonghong.song@linux.dev, eddyz87@gmail.com, brho@google.com,
void@manifault.com, tj@kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] Introduce bpf_preempt_{disable,enable}
Date: Wed, 24 Apr 2024 17:00:37 +0000 [thread overview]
Message-ID: <171397803785.30408.10925797246940135845.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240424031315.2757363-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 24 Apr 2024 03:13:13 +0000 you wrote:
> This set introduces two kfuncs, bpf_preempt_disable and
> bpf_preempt_enable, which are wrappers around preempt_disable and
> preempt_enable in the kernel. These functions allow a BPF program to
> have code sections where preemption is disabled. There are multiple use
> cases that are served by such a feature, a few are listed below:
>
> 1. Writing safe per-CPU alogrithms/data structures that work correctly
> across different contexts.
> 2. Writing safe per-CPU allocators similar to bpf_memalloc on top of
> array/arena memory blobs.
> 3. Writing locking algorithms in BPF programs natively.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Introduce bpf_preempt_[disable,enable] kfuncs
https://git.kernel.org/bpf/bpf-next/c/fc7566ad0a82
- [bpf-next,v2,2/2] selftests/bpf: Add tests for preempt kfuncs
https://git.kernel.org/bpf/bpf-next/c/3134396f1cba
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:[~2024-04-24 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 3:13 [PATCH bpf-next v2 0/2] Introduce bpf_preempt_{disable,enable} Kumar Kartikeya Dwivedi
2024-04-24 3:13 ` [PATCH bpf-next v2 1/2] bpf: Introduce bpf_preempt_[disable,enable] kfuncs Kumar Kartikeya Dwivedi
2024-04-24 3:13 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add tests for preempt kfuncs Kumar Kartikeya Dwivedi
2024-04-24 11:06 ` [PATCH bpf-next v2 0/2] Introduce bpf_preempt_{disable,enable} Jiri Olsa
2024-04-24 17:00 ` 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=171397803785.30408.10925797246940135845.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brho@google.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=tj@kernel.org \
--cc=void@manifault.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