[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160726010344.GO19588@mtj.duckdns.org>
Date: Mon, 25 Jul 2016 21:03:44 -0400
From: Tejun Heo <tj@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Dou Liyang <douly.fnst@...fujitsu.com>, cl@...ux.com,
mika.j.penttila@...il.com, mingo@...hat.com, rjw@...ysocki.net,
hpa@...or.com, yasu.isimatu@...il.com,
isimatu.yasuaki@...fujitsu.com, kamezawa.hiroyu@...fujitsu.com,
izumi.taku@...fujitsu.com, gongzhaogang@...pur.com,
len.brown@...el.com, lenb@...nel.org, tglx@...utronix.de,
chen.tang@...ystack.cn, rafael@...nel.org, x86@...nel.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH v9 0/7] Make cpuid <-> nodeid mapping persistent
Hello,
On Mon, Jul 25, 2016 at 05:25:49PM -0700, Andrew Morton wrote:
> > Yeah, that was one of the early approaches. The issue isn't limited
> > to wq. Any memory allocation can have similar issues of underlying
> > node association changing and we don't have any synchronization
> > mechanism around it. It doesn't make any sense to make NUMA
> > association dynamic when the consumer surface is vastly larger and
> > there's nothing inherently dynamic about the association itself.
>
> And other architectures?
No idea but it only matters for NUMA + CPU hotplug combination where a
whole node can go empty, which would at most be a few archs.
Thanks.
--
tejun
Powered by blists - more mailing lists