From: David Woodhouse <dwmw2@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>
Cc: paulmck@kernel.org, josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
joel@joelfernandes.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org, urezki@gmail.com,
boqun.feng@gmail.com
Subject: Re: [PATCH v2] rcu/nocb: Handle concurrent nocb kthreads creation
Date: Mon, 13 Dec 2021 11:28:45 +0000 [thread overview]
Message-ID: <984a63d4c11d04e2ee8a83fc9c61006413bf209e.camel@infradead.org> (raw)
In-Reply-To: <20211213112246.GA782195@lothringen>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
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.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2021-12-13 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 17:01 Neeraj Upadhyay
2021-12-13 8:18 ` [EXTERNAL] " David Woodhouse
2021-12-13 8:55 ` Neeraj Upadhyay
2021-12-13 11:22 ` Frederic Weisbecker
2021-12-13 11:28 ` David Woodhouse [this message]
2021-12-13 13:14 ` Frederic Weisbecker
2021-12-13 19:00 ` 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=984a63d4c11d04e2ee8a83fc9c61006413bf209e.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®