From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, kafai@fb.com,
andrii@kernel.org, songliubraving@fb.com, haoluo@google.com,
yhs@fb.com, daniel@iogearbox.net, kpsingh@kernel.org,
davem@davemloft.net, kuba@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, tglx@linutronix.de,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next RESEND] bpf: Always use raw spinlock for hash bucket lock
Date: Thu, 22 Sep 2022 01:20:14 +0000 [thread overview]
Message-ID: <166380961488.28833.2007899206692761423.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921073826.2365800-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 21 Sep 2022 15:38:26 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> For a non-preallocated hash map on RT kernel, regular spinlock instead
> of raw spinlock is used for bucket lock. The reason is that on RT kernel
> memory allocation is forbidden under atomic context and regular spinlock
> is sleepable under RT.
>
> [...]
Here is the summary with links:
- [bpf-next,RESEND] bpf: Always use raw spinlock for hash bucket lock
https://git.kernel.org/bpf/bpf-next/c/1d8b82c61329
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:[~2022-09-22 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 7:38 [PATCH bpf-next RESEND] bpf: Always use raw spinlock for hash bucket lock Hou Tao
2022-09-22 1:20 ` 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=166380961488.28833.2007899206692761423.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=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=yhs@fb.com \
/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.