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, 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-next v1 0/3] General enhancements to rqspinlock stress test
Date: Tue, 25 Nov 2025 23:40:10 +0000	[thread overview]
Message-ID: <176411401075.953309.1687282751140868871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251125020749.2421610-1-memxor@gmail.com>

Hello:

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

On Tue, 25 Nov 2025 02:07:46 +0000 you wrote:
> Three enchancements, details in commit messages.
> 
> First, the CPU requirements are 2 for AA, 3 for ABBA, and 4 for ABBCCA,
> hence relax the check during module initialization. Second, add a
> per-CPU histogram to capture lock acquisition times to record which
> buckets these acquisitions fall into for the normal task context and NMI
> context.  Anything below 10ms is not printed in detail, but above that
> displays the full breakdown for each context. Finally, make the delay of
> the NMI and task contexts configurable, set to 10 and 20 ms respectively
> by default.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1,1/3] selftests/bpf: Relax CPU requirements for rqspinlock stress test
    https://git.kernel.org/bpf/bpf-next/c/224de8d5a30e
  - [bpf-next,v1,2/3] selftests/bpf: Add lock wait time stats to rqspinlock stress test
    https://git.kernel.org/bpf/bpf-next/c/6173c1d6208c
  - [bpf-next,v1,3/3] selftests/bpf: Make CS length configurable for rqspinlock stress test
    https://git.kernel.org/bpf/bpf-next/c/88337b587b8b

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



      parent reply	other threads:[~2025-11-25 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  2:07 [PATCH bpf-next v1 0/3] General enhancements to rqspinlock stress test Kumar Kartikeya Dwivedi
2025-11-25  2:07 ` [PATCH bpf-next v1 1/3] selftests/bpf: Relax CPU requirements for " Kumar Kartikeya Dwivedi
2025-11-25  2:07 ` [PATCH bpf-next v1 2/3] selftests/bpf: Add lock wait time stats to " Kumar Kartikeya Dwivedi
2025-11-25  2:07 ` [PATCH bpf-next v1 3/3] selftests/bpf: Make CS length configurable for " Kumar Kartikeya Dwivedi
2025-11-25 23:40 ` 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=176411401075.953309.1687282751140868871.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=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