Re: [PATCH] workqueue: Allocate the unbound pool using local node memory

2015-10-12 Thread Tejun Heo
On Fri, Oct 09, 2015 at 11:53:12AM +0800, Xunlei Pang wrote: > From: Xunlei Pang > > Currently, get_unbound_pool() uses kzalloc() to allocate the > worker pool. Actually, we can use the right node to do the > allocation, achieving local memory access. > > This patch selects target node first, an

Re: [PATCH] workqueue: Allocate the unbound pool using local node memory

2015-10-09 Thread pang . xunlei
Hello, "Hillf Danton" wrote 2015-10-09 PM 06:05:20: > > Re: [PATCH] workqueue: Allocate the unbound pool using local node memory > > > From: Xunlei Pang > > > > Currently, get_unbound_pool() uses kzalloc() to allocate the > > worker pool. Ac

Re: [PATCH] workqueue: Allocate the unbound pool using local node memory

2015-10-09 Thread Hillf Danton
> From: Xunlei Pang > > Currently, get_unbound_pool() uses kzalloc() to allocate the > worker pool. Actually, we can use the right node to do the > allocation, achieving local memory access. > > This patch selects target node first, and uses kzalloc_node() > instead. > > Signed-off-by: Xunlei P

[PATCH] workqueue: Allocate the unbound pool using local node memory

2015-10-08 Thread Xunlei Pang
From: Xunlei Pang Currently, get_unbound_pool() uses kzalloc() to allocate the worker pool. Actually, we can use the right node to do the allocation, achieving local memory access. This patch selects target node first, and uses kzalloc_node() instead. Signed-off-by: Xunlei Pang --- kernel/wor