From: John Fastabend <john.fastabend@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>,
Hou Tao <houtao@huaweicloud.com>,
bpf@vger.kernel.org
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
Hao Luo <haoluo@google.com>,
Daniel Borkmann <daniel@iogearbox.net>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>,
Jiri Olsa <jolsa@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next v2] bpf: Update the comments in maybe_wait_bpf_programs()
Date: Mon, 11 Dec 2023 12:06:16 -0800 [thread overview]
Message-ID: <65776bb8d03f5_e82d208fb@john.notmuch> (raw)
In-Reply-To: <0415f445-4dff-4b64-bd87-f4de08b94bb7@linux.dev>
Yonghong Song wrote:
>
> On 12/11/23 12:34 AM, Hou Tao 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.
> >
> > Signed-off-by: Hou Tao <houtao1@huawei.com>
>
> Acked-by: Yonghong Song <yonghong.song@linux.dev>
>
>
Useful info if you are needing this property.
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2023-12-11 20:06 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 [this message]
2023-12-14 1:10 ` patchwork-bot+netdevbpf
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=65776bb8d03f5_e82d208fb@john.notmuch \
--to=john.fastabend@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox