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, eddyz87@gmail.com,
tj@kernel.org, emil@etsalapatis.com, brho@google.com,
joshdon@google.com, dohyunkim@google.com, kkd@meta.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v5 0/3] Arena Spin Lock
Date: Thu, 06 Mar 2025 06:30:29 +0000 [thread overview]
Message-ID: <174124262975.1146202.289521712611397459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250306035431.2186189-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 5 Mar 2025 19:54:28 -0800 you wrote:
> This set provides an implementation of queued spin lock for arena.
> There is no support for resiliency and recovering from deadlocks yet.
> We will wait for the rqspinlock patch set to land before incorporating
> support.
>
> One minor change compared to the qspinlock algorithm in the kernel is
> that we don't have the trylock fallback when nesting count exceeds 4.
> The maximum number of supported CPUs is 1024, but this can be increased
> in the future if necessary.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] selftests/bpf: Introduce cond_break_label
https://git.kernel.org/bpf/bpf-next/c/994fd3eae1b5
- [bpf-next,v5,2/3] selftests/bpf: Introduce arena spin lock
https://git.kernel.org/bpf/bpf-next/c/0201027a026c
- [bpf-next,v5,3/3] selftests/bpf: Add tests for arena spin lock
https://git.kernel.org/bpf/bpf-next/c/313149fd0a07
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-03-06 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 3:54 [PATCH bpf-next v5 0/3] Arena Spin Lock Kumar Kartikeya Dwivedi
2025-03-06 3:54 ` [PATCH bpf-next v5 1/3] selftests/bpf: Introduce cond_break_label Kumar Kartikeya Dwivedi
2025-03-06 3:54 ` [PATCH bpf-next v5 2/3] selftests/bpf: Introduce arena spin lock Kumar Kartikeya Dwivedi
2025-03-06 3:54 ` [PATCH bpf-next v5 3/3] selftests/bpf: Add tests for " Kumar Kartikeya Dwivedi
2025-03-06 6:30 ` 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=174124262975.1146202.289521712611397459.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=dohyunkim@google.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=joshdon@google.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=tj@kernel.org \
/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.