[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <984a63d4c11d04e2ee8a83fc9c61006413bf209e.camel@infradead.org>
Date: Mon, 13 Dec 2021 11:28:45 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Frederic Weisbecker <frederic@...nel.org>,
Neeraj Upadhyay <quic_neeraju@...cinc.com>
Cc: paulmck@...nel.org, josh@...htriplett.org, rostedt@...dmis.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
joel@...lfernandes.org, rcu@...r.kernel.org,
linux-kernel@...r.kernel.org, urezki@...il.com,
boqun.feng@...il.com
Subject: Re: [PATCH v2] rcu/nocb: Handle concurrent nocb kthreads creation
On Mon, 2021-12-13 at 12:22 +0100, Frederic Weisbecker wrote:
> I was about to ack the patch but, should we really add code that isn't going to
> be necessary before a long while?
Yeah, I'm torn on that. In this case it's harmless enough and it makes
the code reentrant in its own right instead of relying on the fact that
the cpuhp code won't invoke it multiple times in parallel. So I think
that's reasonable defensive programming.
Download attachment "smime.p7s" of type "application/pkcs7-signature" (5174 bytes)
Powered by blists - more mailing lists