public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E . McKenney" <paulmck@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Neeraj Upadhyay <quic_neeraju@quicinc.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Zqiang <qiang1.zhang@intel.com>,
	Uladzislau Rezki <uladzislau.rezki@sony.com>,
	Joel Fernandes <joel@joelfernandes.org>
Subject: [PATCH 0/3] rcu/nocb: Fixes and simplification
Date: Tue, 19 Apr 2022 14:23:17 +0200	[thread overview]
Message-ID: <20220419122320.2060902-1-frederic@kernel.org> (raw)

Hi,

Some updates for the nocb side:

* 1st patch is a simplification on adding/deleting an rdp to a nocb group

* 2nd and 3rd are fixes for the kthread's creation failure path

Frederic Weisbecker (1):
  rcu/nocb: Add/del rdp to iterate from rcuog itself

Zqiang (2):
  rcu: Invert rcu_state.barrier_mutex VS hotplug lock locking order
  rcu/nocb: Fix NOCB kthreads spawn failure with
    rcu_nocb_rdp_deoffload() direct call

 kernel/rcu/tree.h      |   1 +
 kernel/rcu/tree_nocb.h | 226 +++++++++++++++++++++++++----------------
 2 files changed, 139 insertions(+), 88 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-04-19 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 12:23 Frederic Weisbecker [this message]
2022-04-19 12:23 ` [PATCH 1/3] rcu/nocb: Add/del rdp to iterate from rcuog itself Frederic Weisbecker
2022-04-19 12:23 ` [PATCH 2/3] rcu/nocb: Invert rcu_state.barrier_mutex VS hotplug lock locking order Frederic Weisbecker
2022-04-19 12:23 ` [PATCH 3/3] rcu/nocb: Fix NOCB kthreads spawn failure with rcu_nocb_rdp_deoffload() direct call Frederic Weisbecker
2022-04-19 14:18 ` [PATCH 0/3] rcu/nocb: Fixes and simplification 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=20220419122320.2060902-1-frederic@kernel.org \
    --to=frederic@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=qiang1.zhang@intel.com \
    --cc=quic_neeraju@quicinc.com \
    --cc=uladzislau.rezki@sony.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