Re: [PATCH 1/4] workqueue:Fix unbound workqueue's node affinity detection

2014-12-15 Thread Lai Jiangshan
On 12/16/2014 03:32 PM, Kamezawa Hiroyuki wrote: > (2014/12/16 14:30), Lai Jiangshan wrote: >> On 12/15/2014 07:14 PM, Kamezawa Hiroyuki wrote: >>> Unbound wq pool's node attribute is calculated at its allocation. >>> But it's now calculated based on possible cpu<->node information >>> which can be

Re: [PATCH 1/4] workqueue:Fix unbound workqueue's node affinity detection

2014-12-15 Thread Kamezawa Hiroyuki
(2014/12/16 14:30), Lai Jiangshan wrote: On 12/15/2014 07:14 PM, Kamezawa Hiroyuki wrote: Unbound wq pool's node attribute is calculated at its allocation. But it's now calculated based on possible cpu<->node information which can be wrong after cpu hotplug/unplug. If wrong pool->node is set, f

Re: [PATCH 1/4] workqueue:Fix unbound workqueue's node affinity detection

2014-12-15 Thread Lai Jiangshan
On 12/15/2014 07:14 PM, Kamezawa Hiroyuki wrote: > Unbound wq pool's node attribute is calculated at its allocation. > But it's now calculated based on possible cpu<->node information > which can be wrong after cpu hotplug/unplug. > > If wrong pool->node is set, following allocation error will hap

[PATCH 1/4] workqueue:Fix unbound workqueue's node affinity detection

2014-12-15 Thread Kamezawa Hiroyuki
Unbound wq pool's node attribute is calculated at its allocation. But it's now calculated based on possible cpu<->node information which can be wrong after cpu hotplug/unplug. If wrong pool->node is set, following allocation error will happen. == SLUB: Unable to allocate memory on node 2 (gfp=0x8