From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/8] refscale updates for v6.19
Date: Thu, 6 Nov 2025 00:01:42 +0100 [thread overview]
Message-ID: <aQvXVrsgE-Xz_aRB@pavilion.home> (raw)
In-Reply-To: <aQvWCaUWTDvfIUiE@pavilion.home>
Le Wed, Nov 05, 2025 at 11:56:09PM +0100, Frederic Weisbecker a écrit :
> Hi Paul,
>
> Le Sun, Nov 02, 2025 at 02:49:34PM -0800, Paul E. McKenney a écrit :
> > Hello!
> >
> > This series contains additions of microbenchmarks to the refscale suite,
> > and depends on the SRCU series.
> >
> > 1. Exercise DEFINE_STATIC_SRCU_FAST() and init_srcu_struct_fast().
> >
> > 2. Add local_irq_disable() and local_irq_save() readers.
> >
> > 3. Add local_bh_disable() readers.
> >
> > 4. Add preempt_disable() readers.
> >
> > 5. Add this_cpu_inc() readers.
> >
> > 6. Add non-atomic per-CPU increment readers.
> >
> > 7. Do not diable interrupts for tests involving local_bh_enable().
> >
> > 8. Add SRCU-fast-updown readers.
>
> But this series depends on the "RCU Tasks Trace in terms of SRCU-fast"
> patchset which isn't for 6.19, right?
Ah it depends on the latest srcu posting, nevermind, got confused in my
inbox :-)
Thanks.
>
> --
> Frederic Weisbecker
> SUSE Labs
>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2025-11-05 23:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 22:49 Paul E. McKenney
2025-11-02 22:49 ` [PATCH 1/8] refscale: Exercise DEFINE_STATIC_SRCU_FAST() and init_srcu_struct_fast() Paul E. McKenney
2025-11-02 22:49 ` [PATCH 2/8] refscale: Add local_irq_disable() and local_irq_save() readers Paul E. McKenney
2025-11-02 22:49 ` [PATCH 3/8] refscale: Add local_bh_disable() readers Paul E. McKenney
2025-11-11 15:38 ` Sebastian Andrzej Siewior
2025-11-11 19:21 ` Paul E. McKenney
2025-11-12 9:14 ` Sebastian Andrzej Siewior
2025-11-12 17:41 ` Paul E. McKenney
2025-11-02 22:49 ` [PATCH 4/8] refscale: Add preempt_disable() readers Paul E. McKenney
2025-11-02 22:49 ` [PATCH 5/8] refscale: Add this_cpu_inc() readers Paul E. McKenney
2025-11-02 22:49 ` [PATCH 6/8] refscale: Add non-atomic per-CPU increment readers Paul E. McKenney
2025-11-02 22:49 ` [PATCH 7/8] refscale: Do not diable interrupts for tests involving local_bh_enable() Paul E. McKenney
2025-11-02 22:49 ` [PATCH 8/8] refscale: Add SRCU-fast-updown readers Paul E. McKenney
2025-11-05 22:56 ` [PATCH 0/8] refscale updates for v6.19 Frederic Weisbecker
2025-11-05 23:01 ` Frederic Weisbecker [this message]
2025-11-06 1:43 ` Paul E. McKenney
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=aQvXVrsgE-Xz_aRB@pavilion.home \
--to=frederic@kernel.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 \
/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
all inboxes | Powered by JetHome®