RCU Archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Zqiang <qiang.zhang1211@gmail.com>, rcu <rcu@vger.kernel.org>
Subject: Re: [PATCH 0/2] rcu/nocb cleanups
Date: Tue, 16 Jan 2024 08:38:12 -0800	[thread overview]
Message-ID: <938ff17b-f09e-4952-ae54-021a5db9423b@paulmck-laptop> (raw)
In-Reply-To: <20240109222401.28961-1-frederic@kernel.org>

On Tue, Jan 09, 2024 at 11:23:59PM +0100, Frederic Weisbecker wrote:
> Hi,
> 
> This is an excerpt from the "[PATCH 0/8 v2] rcu: Fix expedited GP
> deadlock (and cleanup some nocb stuff)" patchset with only nocb bits
> that were off-topic.
> 
> No change since their previous posting.

Hearing no objections, I have queued this for further review and
testing.

							Thanx, Paul

> Frederic Weisbecker (2):
>   rcu/nocb: Make IRQs disablement symmetric
>   rcu/nocb: Re-arrange call_rcu() NOCB specific code
> 
>  kernel/rcu/tree.c      | 47 +++++++++++++++++++++---------------------
>  kernel/rcu/tree.h      |  9 ++++----
>  kernel/rcu/tree_nocb.h | 38 +++++++++++++++++++++-------------
>  3 files changed, 51 insertions(+), 43 deletions(-)
> 
> -- 
> 2.43.0
> 

      parent reply	other threads:[~2024-01-16 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 22:23 [PATCH 0/2] rcu/nocb cleanups Frederic Weisbecker
2024-01-09 22:24 ` [PATCH 1/2] rcu/nocb: Make IRQs disablement symmetric Frederic Weisbecker
2024-01-09 22:24 ` [PATCH 2/2] rcu/nocb: Re-arrange call_rcu() NOCB specific code Frederic Weisbecker
2024-01-16 16:38 ` Paul E. McKenney [this message]

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=938ff17b-f09e-4952-ae54-021a5db9423b@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neeraj.upadhyay@amd.com \
    --cc=qiang.zhang1211@gmail.com \
    --cc=rcu@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).