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>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org, Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Uladzislau Rezki <urezki@gmail.com>
Subject: [PATCH 0/2] rcu/nocb fix and optimization
Date: Tue, 11 Oct 2022 00:39:54 +0200 [thread overview]
Message-ID: <20221010223956.1041247-1-frederic@kernel.org> (raw)
I wanted to send this a few days ago but then I faced a TREE01 stall
(rcu_barrier() related). I just couldn't remember if it was before or
after these patches... But finally looking at the log, I found the
head which is e8c56bb5baa6969bf2d01b8619f22f5a71818497 (an old RCU:dev
head from more than a month ago, way before these patches). Phew!
Anyway I re-launched many times TREE01 on latest RCU:dev before and
after these patches, it has run both ways more than 600 hours without
any issue...
Frederic Weisbecker (2):
rcu: Fix missing nocb gp wake on rcu_barrier()
rcu/nocb: Spare bypass locking upon normal enqueue
kernel/rcu/tree.c | 6 ++++++
kernel/rcu/tree.h | 1 +
kernel/rcu/tree_nocb.h | 11 +++++++++--
3 files changed, 16 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2022-10-10 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 22:39 Frederic Weisbecker [this message]
2022-10-10 22:39 ` [PATCH 1/2] rcu: Fix missing nocb gp wake on rcu_barrier() Frederic Weisbecker
2022-10-11 2:01 ` Joel Fernandes
2022-10-11 7:25 ` Paul E. McKenney
2022-10-11 7:33 ` Joel Fernandes
2022-10-10 22:39 ` [PATCH 2/2] rcu/nocb: Spare bypass locking upon normal enqueue Frederic Weisbecker
2022-10-11 2:00 ` Joel Fernandes
2022-10-11 2:08 ` Joel Fernandes
2022-10-11 19:21 ` Frederic Weisbecker
2022-10-11 23:47 ` Joel Fernandes
2022-10-12 10:23 ` Frederic Weisbecker
2022-10-12 14:49 ` 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=20221010223956.1041247-1-frederic@kernel.org \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.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 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.