[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <130ce800-1bcd-47c0-9058-48e820738852@paulmck-laptop>
Date: Tue, 22 Apr 2025 16:06:28 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Joel Fernandes <joelagnelf@...dia.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@...il.com>,
Joel Fernandes <joel@...lfernandes.org>, RCU <rcu@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <frederic@...nel.org>,
Neeraj upadhyay <Neeraj.Upadhyay@....com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>
Subject: Re: [PATCH] tools/memory-model/Documentation: Fix SRCU section in
explanation.txt
On Tue, Apr 22, 2025 at 06:56:17PM -0400, Joel Fernandes wrote:
>
>
> On 4/22/2025 6:55 PM, Joel Fernandes wrote:
> >
> >
> > On 4/22/2025 1:56 PM, Paul E. McKenney wrote:
> >> On Tue, Apr 22, 2025 at 07:38:30PM +0200, Uladzislau Rezki (Sony) wrote:
> >>> The SRCU read-side critical sections describes the difference between
> >>> srcu_down_read()/srcu_up_read() and srcu_read_lock()/srcu_read_unlock()
> >>> in a way that a last pair must occur on the same CPU.
> >>>
> >>> This is not true, the srcu_read_unlock() can happen on any CPU, but it
> >>> must be performed by the same task that invoked srcu_read_lock().
> >>>
> >>> Signed-off-by: Uladzislau Rezki (Sony) <urezki@...il.com>
> >>
> >> Good catch!
> >>
> >> Reviewed-by: Paul E. McKenney <paulmck@...nel.org>
> >
> > Applied, thanks.
> >
>
> Oops, though this is memory model and not RCU per-se. Paul do you want to take
> it or should I? ;)
Heh! I will take this one. One of those days, I guess!
Thanx, Pau
Powered by blists - more mailing lists