From: Joel Fernandes <joelagnelf@nvidia.com>
To: paulmck@kernel.org, "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
RCU <rcu@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH] tools/memory-model/Documentation: Fix SRCU section in explanation.txt
Date: Tue, 22 Apr 2025 18:55:16 -0400 [thread overview]
Message-ID: <1a9388fb-83ff-4345-ab2b-6c1825913d71@nvidia.com> (raw)
In-Reply-To: <1497ef3c-b1fc-4723-949b-28d92a3afb6b@paulmck-laptop>
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@gmail.com>
>
> Good catch!
>
> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
Applied, thanks.
next prev parent reply other threads:[~2025-04-22 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 17:38 [PATCH] tools/memory-model/Documentation: Fix SRCU section in explanation.txt Uladzislau Rezki (Sony)
2025-04-22 17:56 ` Paul E. McKenney
2025-04-22 22:55 ` Joel Fernandes [this message]
2025-04-22 22:56 ` Joel Fernandes
2025-04-22 23:06 ` 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=1a9388fb-83ff-4345-ab2b-6c1825913d71@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--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