From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
kkd@meta.com, kernel-team@meta.com
Subject: [PATCH bpf-next v1 0/3] General enhancements to rqspinlock stress test
Date: Tue, 25 Nov 2025 02:07:46 +0000 [thread overview]
Message-ID: <20251125020749.2421610-1-memxor@gmail.com> (raw)
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.
Kumar Kartikeya Dwivedi (3):
selftests/bpf: Relax CPU requirements for rqspinlock stress test
selftests/bpf: Add lock wait time stats to rqspinlock stress test
selftests/bpf: Make CS length configurable for rqspinlock stress test
.../bpf/test_kmods/bpf_test_rqspinlock.c | 120 +++++++++++++++++-
1 file changed, 117 insertions(+), 3 deletions(-)
base-commit: 590699d85823f38b74d52a0811ef22ebb61afddc
--
2.51.0
next reply other threads:[~2025-11-25 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 2:07 Kumar Kartikeya Dwivedi [this message]
2025-11-25 2:07 ` [PATCH bpf-next v1 1/3] selftests/bpf: Relax CPU requirements for rqspinlock stress test 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 ` [PATCH bpf-next v1 0/3] General enhancements to " 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=20251125020749.2421610-1-memxor@gmail.com \
--to=memxor@gmail.com \
--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 \
/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