From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>
Cc: <tj@kernel.org>, <laijs@cn.fujitsu.com>,
<isimatu.yasuaki@jp.fujitsu.com>,
<kamezawa.hiroyu@jp.fujitsu.com>, <tangchen@cn.fujitsu.com>,
<guz.fnst@cn.fujitsu.com>, <izumi.taku@jp.fujitsu.com>
Subject: [PATCH 2/2] workqueue: update per cpu workqueue's numa affinity when cpu preparing online
Date: Thu, 26 Mar 2015 10:17:55 +0800 [thread overview]
Message-ID: <1427336275-32066-3-git-send-email-guz.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <1427336275-32066-1-git-send-email-guz.fnst@cn.fujitsu.com>
Update the per cpu workqueue's numa affinity when cpu preparing online to
create the worker on the correct node.
Signed-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>
---
kernel/workqueue.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 41ff75b..4c65953 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -4618,6 +4618,7 @@ static int workqueue_cpu_up_callback(struct notifier_block *nfb,
switch (action & ~CPU_TASKS_FROZEN) {
case CPU_UP_PREPARE:
for_each_cpu_worker_pool(pool, cpu) {
+ pool->node = cpu_to_node(cpu);
if (pool->nr_workers)
continue;
if (!create_worker(pool))
--
1.7.7
next prev parent reply other threads:[~2015-03-26 2:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 2:17 [PATCH 0/2] workqueue: fix a bug when numa mapping is changed Gu Zheng
2015-03-26 2:17 ` [PATCH 1/2] x86/cpu hotplug: make apicid <--> cpuid mapping persistent Gu Zheng
2015-03-26 3:19 ` Kamezawa Hiroyuki
2015-03-26 4:55 ` Gu Zheng
2015-03-26 15:13 ` Tejun Heo
2015-03-26 16:31 ` Kamezawa Hiroyuki
2015-03-30 9:58 ` Gu Zheng
2015-04-01 2:59 ` Kamezawa Hiroyuki
2015-03-26 2:17 ` Gu Zheng [this message]
2015-03-26 3:12 ` [PATCH 0/2] workqueue: fix a bug when numa mapping is changed Kamezawa Hiroyuki
2015-03-26 5:04 ` Gu Zheng
2015-03-26 15:18 ` Tejun Heo
2015-03-26 16:42 ` Kamezawa Hiroyuki
2015-03-30 9:49 ` Gu Zheng
2015-03-30 9:49 ` Gu Zheng
2015-03-31 6:09 ` Kamezawa Hiroyuki
2015-03-31 15:28 ` Tejun Heo
2015-04-01 2:55 ` Kamezawa Hiroyuki
2015-04-01 3:02 ` Tejun Heo
2015-04-01 3:05 ` Tejun Heo
2015-04-01 8:30 ` Kamezawa Hiroyuki
2015-04-02 1:36 ` Gu Zheng
2015-04-02 2:54 ` Kamezawa Hiroyuki
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=1427336275-32066-3-git-send-email-guz.fnst@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=tj@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).