[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1427336275-32066-1-git-send-email-guz.fnst@cn.fujitsu.com>
Date: Thu, 26 Mar 2015 10:17:53 +0800
From: Gu Zheng <guz.fnst@...fujitsu.com>
To: <linux-kernel@...r.kernel.org>
CC: <tj@...nel.org>, <laijs@...fujitsu.com>,
<isimatu.yasuaki@...fujitsu.com>, <kamezawa.hiroyu@...fujitsu.com>,
<tangchen@...fujitsu.com>, <guz.fnst@...fujitsu.com>,
<izumi.taku@...fujitsu.com>
Subject: [PATCH 0/2] workqueue: fix a bug when numa mapping is changed
Yasuaki Ishimatsu found that with node online/offline, cpu<->node
relationship is established. Because workqueue uses a info which was
established at boot time, but it may be changed by node hotpluging.
Once pool->node points to a stale node, following allocation failure
happens.
==
SLUB: Unable to allocate memory on node 2 (gfp=0x80d0)
cache: kmalloc-192, object size: 192, buffer size: 192, default
order:
1, min order: 0
node 0: slabs: 6172, objs: 259224, free: 245741
node 1: slabs: 3261, objs: 136962, free: 127656
==
As the apicid <--> node relationship is persistent, so the root cause is the
cpu-id <-> lapicid mapping is not persistent (because the currently implementation
always choose the first free cpu id for the new added cpu), so if we can build
persistent cpu-id <-> lapicid relationship, this problem will be fixed.
Please refer to https://lkml.org/lkml/2015/2/27/145 for the previous discussion.
Gu Zheng (2):
x86/cpu hotplug: make lapicid <-> cpuid mapping persistent
workqueue: update per cpu workqueue's numa affinity when cpu
preparing online
arch/x86/kernel/apic/apic.c | 31 ++++++++++++++++++++++++++++++-
kernel/workqueue.c | 1 +
2 files changed, 31 insertions(+), 1 deletions(-)
--
1.7.7
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists