From: Joel Fernandes <joelagnelf@nvidia.com>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelagnelf@nvidia.com>
Subject: [PATCH 0/3] rcu_seq_done_exact() improvements
Date: Mon, 24 Mar 2025 13:01:52 -0400 [thread overview]
Message-ID: <20250324170156.469763-1-joelagnelf@nvidia.com> (raw)
These are small improvements to rcu_seq_done_exact() improving its readability
and adding error checking. Passes rcutorture testing. Will send the rcutorture
wrap around testing separately.
Frederic Weisbecker (1):
rcu: Comment on the extraneous delta test on rcu_seq_done_exact()
Joel Fernandes (2):
rcu: Replace magic number with meaningful constant in
rcu_seq_done_exact()
rcu: Add warning to ensure rcu_seq_done_exact() is working
kernel/rcu/rcu.h | 14 +++++++++++++-
kernel/rcu/tree.c | 5 +++++
2 files changed, 18 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-03-24 17:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:01 Joel Fernandes [this message]
2025-03-24 17:01 ` [PATCH 1/3] rcu: Replace magic number with meaningful constant in rcu_seq_done_exact() Joel Fernandes
2025-03-26 22:33 ` Paul E. McKenney
2025-03-26 22:42 ` Joel Fernandes
2025-03-27 17:09 ` Paul E. McKenney
2025-03-28 2:31 ` Joel Fernandes
2025-03-30 22:10 ` Frederic Weisbecker
2025-03-31 18:28 ` Paul E. McKenney
2025-03-31 21:14 ` Frederic Weisbecker
2025-03-31 21:29 ` Paul E. McKenney
2025-04-01 13:38 ` Frederic Weisbecker
2025-04-02 4:24 ` Paul E. McKenney
2025-03-24 17:01 ` [PATCH 2/3] rcu: Add warning to ensure rcu_seq_done_exact() is working Joel Fernandes
2025-03-26 22:36 ` Paul E. McKenney
2025-03-26 22:50 ` Joel Fernandes
2025-03-26 23:21 ` Paul E. McKenney
2025-03-24 17:01 ` [PATCH 3/3] rcu: Comment on the extraneous delta test on rcu_seq_done_exact() Joel Fernandes
2025-03-26 22:37 ` Paul E. McKenney
2025-03-26 22:51 ` Joel Fernandes
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=20250324170156.469763-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®