From: Tejun Heo <tj@kernel.org>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org,
Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: [PATCH] workqueue: Ensure that cpumask set for pools created after boot
Date: Tue, 23 May 2017 16:10:29 -0400 [thread overview]
Message-ID: <20170523201029.GH13222@htj.duckdns.org> (raw)
In-Reply-To: <d757731e-8770-05a0-9d39-9b296bdccd52@linux.vnet.ibm.com>
Hello,
On Tue, May 23, 2017 at 03:09:07PM -0500, Michael Bringmann wrote:
> To confirm, you want the WARN_ON(cpumask_any(pool->attrs->cpumask) >= NR_CPUS)
> at the point where I place my current patch?
Yeah, cpumask_weight() probably is a bit more intuitive but I'm
curious why we're creating workqueues for a node before cpus come
online.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-05-23 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 16:48 Michael Bringmann
2017-05-10 17:33 ` Tejun Heo
2017-05-15 15:48 ` Michael Bringmann
2017-05-16 15:55 ` Tejun Heo
2017-05-23 19:44 ` Michael Bringmann
2017-05-23 19:49 ` Tejun Heo
2017-05-23 20:09 ` Michael Bringmann
2017-05-23 20:10 ` Tejun Heo [this message]
2017-05-24 16:30 ` Michael Bringmann
2017-05-24 23:39 ` Michael Bringmann
2017-05-25 15:03 ` Tejun Heo
2017-05-25 15:07 ` Tejun Heo
2017-05-25 15:30 ` Michael Bringmann
2017-06-06 16:18 ` Michael Bringmann
2017-06-06 18:09 ` Tejun Heo
2017-06-12 14:47 ` Michael Bringmann
2017-06-12 16:14 ` Tejun Heo
2017-06-12 17:10 ` Michael Bringmann
2017-06-12 17:32 ` Tejun Heo
2017-06-13 20:04 ` Michael Bringmann
2017-06-13 20:10 ` Tejun Heo
2017-06-28 21:15 ` Michael Bringmann
2017-06-28 21:24 ` Tejun Heo
2017-07-26 15:25 ` Michael Bringmann
2017-07-26 19:16 ` Tejun Heo
2017-07-27 17:04 ` Michael Bringmann
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=20170523201029.GH13222@htj.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.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
Powered by JetHome