From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: ast@kernel.org, paulmck@kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, joelagnelf@nvidia.com,
josh@joshtriplett.org, boqun.feng@gmail.com, urezki@gmail.com,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, qiang.zhang@linux.dev,
daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/7] bpf: introduce and use rcu_read_lock_dont_migrate
Date: Tue, 26 Aug 2025 05:40:14 +0000 [thread overview]
Message-ID: <175618681450.3665841.12074652835342270974.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250821090609.42508-1-dongml2@chinatelecom.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 21 Aug 2025 17:06:02 +0800 you wrote:
> migrate_disable() and rcu_read_lock() are used to together in many case in
> bpf. However, when PREEMPT_RCU is not enabled, rcu_read_lock() will
> disable preemption, which indicate migrate_disable(), so we don't need to
> call it in this case.
>
> In this series, we introduce rcu_read_lock_dont_migrate and
> rcu_read_unlock_migrate, which will call migrate_disable and
> migrate_enable only when PREEMPT_RCU enabled. And use
> rcu_read_lock_dont_migrate in bpf subsystem.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/7] rcu: add rcu_read_lock_dont_migrate()
https://git.kernel.org/bpf/bpf-next/c/1b93c03fb319
- [bpf-next,v3,2/7] bpf: use rcu_read_lock_dont_migrate() for bpf_cgrp_storage_free()
https://git.kernel.org/bpf/bpf-next/c/8c0afc7c9c11
- [bpf-next,v3,3/7] bpf: use rcu_read_lock_dont_migrate() for bpf_inode_storage_free()
https://git.kernel.org/bpf/bpf-next/c/f2fa9b906911
- [bpf-next,v3,4/7] bpf: use rcu_read_lock_dont_migrate() for bpf_iter_run_prog()
https://git.kernel.org/bpf/bpf-next/c/68748f0397a3
- [bpf-next,v3,5/7] bpf: use rcu_read_lock_dont_migrate() for bpf_task_storage_free()
https://git.kernel.org/bpf/bpf-next/c/cf4303b70dfa
- [bpf-next,v3,6/7] bpf: use rcu_read_lock_dont_migrate() for bpf_prog_run_array_cg()
https://git.kernel.org/bpf/bpf-next/c/427a36bb5504
- [bpf-next,v3,7/7] bpf: use rcu_read_lock_dont_migrate() for trampoline.c
https://git.kernel.org/bpf/bpf-next/c/8e4f0b1ebcf2
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:[~2025-08-26 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 9:06 Menglong Dong
2025-08-21 9:06 ` [PATCH bpf-next v3 1/7] rcu: add rcu_read_lock_dont_migrate() Menglong Dong
2025-08-21 11:41 ` Paul E. McKenney
2025-08-21 9:06 ` [PATCH bpf-next v3 2/7] bpf: use rcu_read_lock_dont_migrate() for bpf_cgrp_storage_free() Menglong Dong
2025-08-21 9:06 ` [PATCH bpf-next v3 3/7] bpf: use rcu_read_lock_dont_migrate() for bpf_inode_storage_free() Menglong Dong
2025-08-21 9:06 ` [PATCH bpf-next v3 4/7] bpf: use rcu_read_lock_dont_migrate() for bpf_iter_run_prog() Menglong Dong
2025-08-21 9:06 ` [PATCH bpf-next v3 5/7] bpf: use rcu_read_lock_dont_migrate() for bpf_task_storage_free() Menglong Dong
2025-08-21 9:06 ` [PATCH bpf-next v3 6/7] bpf: use rcu_read_lock_dont_migrate() for bpf_prog_run_array_cg() Menglong Dong
2025-08-21 9:06 ` [PATCH bpf-next v3 7/7] bpf: use rcu_read_lock_dont_migrate() for trampoline.c Menglong Dong
2025-08-26 5: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=175618681450.3665841.12074652835342270974.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=frederic@kernel.org \
--cc=haoluo@google.com \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=josh@joshtriplett.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®