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/3] rcu/nocb updates v2
Date: Mon, 4 Dec 2023 20:20:56 -0800 [thread overview]
Message-ID: <08b4d5bf-800b-4696-8c4d-fc86af741849@paulmck-laptop> (raw)
In-Reply-To: <20231115191128.15615-1-frederic@kernel.org>
On Wed, Nov 15, 2023 at 02:11:25PM -0500, Frederic Weisbecker wrote:
> Hi,
>
> Here is a re-issue of some leftovers from a previous patchset.
> Changes since last time:
>
> 1) Use rcu_get_jiffies_lazy_flush() instead of the raw variable (thanks Joel)
> 2) Further comment ordering expectations between grace period end and
> callbacks execution.
Hearing no objections, I have queued these for further review and testing.
Thanx, Paul
> Thanks.
>
> Frederic Weisbecker (3):
> rcu: Rename jiffies_till_flush to jiffies_lazy_flush
> rcu/nocb: Remove needless LOAD-ACQUIRE
> rcu/nocb: Remove needless full barrier after callback advancing
>
> kernel/rcu/rcu.h | 8 ++++----
> kernel/rcu/rcuscale.c | 6 +++---
> kernel/rcu/tree.c | 6 ++++++
> kernel/rcu/tree_nocb.h | 26 ++++++++++++--------------
> 4 files changed, 25 insertions(+), 21 deletions(-)
>
> --
> 2.42.1
>
prev parent reply other threads:[~2023-12-05 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 19:11 [PATCH 0/3] rcu/nocb updates v2 Frederic Weisbecker
2023-11-15 19:11 ` [PATCH 1/3] rcu: Rename jiffies_till_flush to jiffies_lazy_flush Frederic Weisbecker
2023-11-15 19:11 ` [PATCH 2/3] rcu/nocb: Remove needless LOAD-ACQUIRE Frederic Weisbecker
2023-11-15 19:11 ` [PATCH 3/3] rcu/nocb: Remove needless full barrier after callback advancing Frederic Weisbecker
2023-12-05 4:20 ` 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=08b4d5bf-800b-4696-8c4d-fc86af741849@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).