From: Neeraj Upadhyay <Neeraj.Upadhyay@kernel.org>
To: rcu@vger.kernel.org
Cc: paulmck@kernel.org, joel@joelfernandes.org, frederic@kernel.org,
boqun.feng@gmail.com, urezki@gmail.com,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org, christophe.jaillet@wanadoo.fr
Subject: [PATCH rcu 00/14] RCU scaling tests updates for v6.12
Date: Fri, 16 Aug 2024 12:32:09 +0530 [thread overview]
Message-ID: <20240816070209.GA60666@neeraj.linux> (raw)
Hello,
Following are the rcuscale and refscale updates for v6.12:
1. Add TINY scenario, courtesy of Paul E. McKenney.
2. Optimize process_durations(), courtesy of Christophe JAILLET.
3. Save a few lines with whitespace-only change, courtesy of
Paul E. McKenney.
4. Dump stacks of stalled rcu_scale_writer() instances,
courtesy of Paul E. McKenney.
5. Dump grace-period statistics when rcu_scale_writer() stalls,
courtesy of Paul E. McKenney.
6. Mark callbacks not currently participating in barrier operation,
courtesy of Paul E. McKenney.
7. Print detailed grace-period and barrier diagnostics, courtesy of
Paul E. McKenney.
8. Provide clear error when async specified without primitives,
courtesy of Paul E. McKenney.
9. Make all writer tasks report upon hang, courtesy of Paul E. McKenney.
10. Make rcu_scale_writer() tolerate repeated GFP_KERNEL failure,
courtesy of Paul E. McKenney.
11. Use special allocator for rcu_scale_writer(), courtesy of
Paul E. McKenney.
12. NULL out top-level pointers to heap memory, courtesy of
Paul E. McKenney.
13. Count outstanding callbacks per-task rather than per-CPU,
courtesy of Paul E. McKenney.
14. Constify struct ref_scale_ops, courtesy of Christophe JAILLET.
Git tree: https://git.kernel.org/pub/scm/linux/kernel/git/neeraj.upadhyay/linux-rcu.git/log/?h=rcu_scaling_tests.15.08.24a
(rebased on top of rcu.tasks.14.08.24a due to commit dependency)
- Neeraj
------------------------------------------------------------------------
kernel/rcu/rcuscale.c | 212 +++++++++++++++---
kernel/rcu/refscale.c | 67 +++---
kernel/rcu/tree.c | 3 +
.../rcutorture/configs/refscale/TINY | 20 ++
4 files changed, 245 insertions(+), 57 deletions(-)
create mode 100644 tools/testing/selftests/rcutorture/configs/refscale/TINY
next reply other threads:[~2024-08-16 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:02 Neeraj Upadhyay [this message]
2024-08-16 7:02 ` [PATCH rcu 01/14] refscale: Add TINY scenario neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 02/14] refscale: Optimize process_durations() neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 03/14] rcuscale: Save a few lines with whitespace-only change neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 04/14] rcuscale: Dump stacks of stalled rcu_scale_writer() instances neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 05/14] rcuscale: Dump grace-period statistics when rcu_scale_writer() stalls neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 06/14] rcu: Mark callbacks not currently participating in barrier operation neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 07/14] rcuscale: Print detailed grace-period and barrier diagnostics neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 08/14] rcuscale: Provide clear error when async specified without primitives neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 09/14] rcuscale: Make all writer tasks report upon hang neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 10/14] rcuscale: Make rcu_scale_writer() tolerate repeated GFP_KERNEL failure neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 11/14] rcuscale: Use special allocator for rcu_scale_writer() neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 12/14] rcuscale: NULL out top-level pointers to heap memory neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 13/14] rcuscale: Count outstanding callbacks per-task rather than per-CPU neeraj.upadhyay
2024-08-16 7:02 ` [PATCH rcu 14/14] refscale: Constify struct ref_scale_ops neeraj.upadhyay
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=20240816070209.GA60666@neeraj.linux \
--to=neeraj.upadhyay@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@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