BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, josef@toxicpanda.com, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
	eddyz87@gmail.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v2] rqspinlock: Choose trylock fallback for NMI waiters
Date: Tue, 09 Sep 2025 22:20:19 +0000	[thread overview]
Message-ID: <175745641999.833608.430490724192273857.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250909184959.3509085-1-memxor@gmail.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue,  9 Sep 2025 18:49:59 +0000 you wrote:
> Currently, out of all 3 types of waiters in the rqspinlock slow path
> (i.e., pending bit waiter, wait queue head waiter, and wait queue
> non-head waiter), only the pending bit waiter and wait queue head
> waiters apply deadlock checks and a timeout on their waiting loop. The
> assumption here was that the wait queue head's forward progress would be
> sufficient to identify cases where the lock owner or pending bit waiter
> is stuck, and non-head waiters relying on the head waiter would prove to
> be sufficient for their own forward progress.
> 
> [...]

Here is the summary with links:
  - [bpf,v2] rqspinlock: Choose trylock fallback for NMI waiters
    https://git.kernel.org/bpf/bpf/c/0d80e7f951be

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-09-09 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 18:49 [PATCH bpf v2] rqspinlock: Choose trylock fallback for NMI waiters Kumar Kartikeya Dwivedi
2025-09-09 22: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=175745641999.833608.430490724192273857.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=eddyz87@gmail.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@meta.com \
    --cc=kkd@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox