RCU Archive mirror
 help / color / mirror / Atom feed

From: "Neeraj Upadhyay (AMD)" <neeraj.iitr10@gmail.com>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	rostedt@goodmis.org, paulmck@kernel.org, Neeraj.Upadhyay@amd.com
Subject: [PATCH rcu 0/3] SRCU updates for v6.8
Date: Tue, 12 Dec 2023 23:17:50 +0530	[thread overview]
Message-ID: <20231212174750.GA11886@neeraj.linux> (raw)

Hello,

This series contains SRCU updates:

1.      Remove superfluous callbacks advancing from srcu_gp_start(),
        courtesy of Frederic Weisbecker.

2.      No need to advance/accelerate if no callback enqueued, courtesy
        of Frederic Weisbecker.

3.      Explain why callbacks invocations can't run concurrently,
        courtesy of Frederic Weisbecker.


Thanks
Neeraj

------------------------------------------------------------------------

 b/kernel/rcu/srcutree.c |   10 ----------
 kernel/rcu/srcutree.c   |   14 +++++++++++---
 2 files changed, 11 insertions(+), 13 deletions(-)

next             reply	other threads:[~2023-12-12 17:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 17:47 Neeraj Upadhyay (AMD) [this message]
2023-12-12 17:48 ` [PATCH rcu 1/3] srcu: Remove superfluous callbacks advancing from srcu_gp_start() Neeraj Upadhyay (AMD)
2023-12-12 17:48 ` [PATCH rcu 2/3] srcu: No need to advance/accelerate if no callback enqueued Neeraj Upadhyay (AMD)
2023-12-12 17:48 ` [PATCH rcu 3/3] srcu: Explain why callbacks invocations can't run concurrently Neeraj Upadhyay (AMD)
2023-12-13 14:27   ` Joel Fernandes
2023-12-13 17:52     ` Paul E. McKenney
2023-12-13 18:35       ` Joel Fernandes
2023-12-13 18:55         ` Paul E. McKenney
2023-12-13 19:01           ` Joel Fernandes
2023-12-13 18:18 ` [PATCH rcu 4/3] srcu: Use try-lock lockdep annotation for NMI-safe access Neeraj Upadhyay (AMD)

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=20231212174750.GA11886@neeraj.linux \
    --to=neeraj.iitr10@gmail.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).