[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <22e77bf0-9af3-4ed1-b0c9-768ae5c06620@paulmck-laptop>
Date: Fri, 28 Jun 2024 13:03:06 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org, kernel-team@...a.com,
rostedt@...dmis.org
Subject: Re: [PATCH rcu 3/6 v2] rcu/exp: Remove superfluous full memory
barrier upon first EQS snapshot
On Fri, Jun 28, 2024 at 01:20:55PM +0200, Frederic Weisbecker wrote:
> Le Thu, Jun 27, 2024 at 11:53:29AM -0700, Paul E. McKenney a écrit :
> > On Thu, Jun 27, 2024 at 01:36:58PM +0200, Frederic Weisbecker wrote:
> > > When the grace period kthread checks the extended quiescent state
> > > counter of a CPU, full ordering is necessary to ensure that either:
> >
> > Just to make sure that I understand...
> >
> > I need to replace these commits in -rcu:
> >
> > da979d0162fc6 rcu: Remove full ordering on second EQS snapshot
> > 6411f4185f657 rcu: Remove superfluous full memory barrier upon first EQS snapshot
> > dec56ca5f1c34 rcu/exp: Remove superfluous full memory barrier upon first EQS snapshot
> >
> > With these three patches, and keep these three commits as they are?
> >
> > d43a302fc08a5 rcu: Remove full memory barrier on boot time eqs sanity check
> > b1c36aa90cbf1 rcu: Remove full memory barrier on RCU stall printout
> > 64d68f1d53f77 rcu/exp: Remove redundant full memory barrier at the end of GP
>
> Exactly! Those were the precisions I forgot to mention.
Done, and started testing. If all goes well, this might make tomorrow's
-next.
Thanx, Paul
Powered by blists - more mailing lists