From: Christoph Hellwig <hch@infradead.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 1/5] torture: Remove support for SRCU-lite
Date: Wed, 25 Jun 2025 05:05:47 -0700 [thread overview]
Message-ID: <aFvmG2lT65Ido1fq@infradead.org> (raw)
In-Reply-To: <20250624161400.867880-1-paulmck@kernel.org>
On Tue, Jun 24, 2025 at 09:13:56AM -0700, Paul E. McKenney wrote:
> Because SRCU-lite is being replaced by SRCU-fast, this commit removes
> support for SRCU-lite from refscale.c.
Please explain how they different and why one is a good enough (or
even better?) replacement for the other.
next prev parent reply other threads:[~2025-06-25 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 16:13 [PATCH 0/5] Remove SRCU-lite in favor of SRCU-fast Paul E. McKenney
2025-06-24 16:13 ` [PATCH 1/5] torture: Remove support for SRCU-lite Paul E. McKenney
2025-06-25 12:05 ` Christoph Hellwig [this message]
2025-06-26 10:54 ` Paul E. McKenney
2025-06-26 11:03 ` Christoph Hellwig
2025-06-26 14:37 ` Paul E. McKenney
2025-06-24 16:13 ` [PATCH 2/5] rcutorture: Remove SRCU-lite scenarios Paul E. McKenney
2025-06-24 16:13 ` [PATCH 3/5] rcutorture: Remove support for SRCU-lite Paul E. McKenney
2025-06-24 16:13 ` [PATCH 4/5] srcu: Remove SRCU-lite implementation Paul E. McKenney
2025-06-24 16:14 ` [PATCH 5/5] checkpatch: Remove SRCU-lite deprecation Paul E. McKenney
2025-07-02 0:23 ` [PATCH v2 0/5] Remove SRCU-lite in favor of SRCU-fast Paul E. McKenney
2025-07-02 0:23 ` [PATCH v2 1/5] torture: Remove support for SRCU-lite Paul E. McKenney
2025-07-02 0:23 ` [PATCH v2 2/5] rcutorture: Remove SRCU-lite scenarios Paul E. McKenney
2025-07-02 0:23 ` [PATCH v2 3/5] rcutorture: Remove support for SRCU-lite Paul E. McKenney
2025-07-02 0:23 ` [PATCH v2 4/5] srcu: Remove SRCU-lite implementation Paul E. McKenney
2025-07-02 0:23 ` [PATCH v2 5/5] checkpatch: Remove SRCU-lite deprecation 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=aFvmG2lT65Ido1fq@infradead.org \
--to=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.