From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v2] bpf: Update the comments in maybe_wait_bpf_programs()
Date: Thu, 14 Dec 2023 01:10:23 +0000 [thread overview]
Message-ID: <170251622375.21032.3667664124559774409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231211083447.1921178-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 11 Dec 2023 16:34:47 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Since commit 638e4b825d52 ("bpf: Allows per-cpu maps and map-in-map in
> sleepable programs"), sleepable BPF program can also use map-in-map, but
> maybe_wait_bpf_programs() doesn't handle it accordingly. The main reason
> is that using synchronize_rcu_tasks_trace() to wait for the completions
> of these sleepable BPF programs may incur a very long delay and
> userspace may think it is hung, so the wait for sleepable BPF programs
> is skipped. Update the comments in maybe_wait_bpf_programs() to reflect
> the reason.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: Update the comments in maybe_wait_bpf_programs()
https://git.kernel.org/bpf/bpf-next/c/2a0c6b41eec9
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:[~2023-12-14 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 8:34 [PATCH bpf-next v2] bpf: Update the comments in maybe_wait_bpf_programs() Hou Tao
2023-12-11 14:58 ` Yonghong Song
2023-12-11 20:06 ` John Fastabend
2023-12-14 1:10 ` 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=170251622375.21032.3667664124559774409.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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.