From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dou Liyang <douly.fnst@cn.fujitsu.com>,
cl@linux.com, mika.j.penttila@gmail.com, mingo@redhat.com,
rjw@rjwysocki.net, hpa@zytor.com, yasu.isimatu@gmail.com,
isimatu.yasuaki@jp.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com,
izumi.taku@jp.fujitsu.com, gongzhaogang@inspur.com,
len.brown@intel.com, lenb@kernel.org, tglx@linutronix.de,
chen.tang@easystack.cn, rafael@kernel.org, x86@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v9 0/7] Make cpuid <-> nodeid mapping persistent
Date: Mon, 25 Jul 2016 21:03:44 -0400 [thread overview]
Message-ID: <20160726010344.GO19588@mtj.duckdns.org> (raw)
In-Reply-To: <20160725172549.e5a23d495a356f026fbb28fa@linux-foundation.org>
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-07-26 1:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 8:35 [PATCH v9 0/7] Make cpuid <-> nodeid mapping persistent Dou Liyang
2016-07-25 8:35 ` [PATCH v9 1/7] x86, memhp, numa: Online memory-less nodes at boot time Dou Liyang
2016-07-25 8:35 ` [PATCH v9 2/7] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus " Dou Liyang
2016-07-25 8:35 ` [PATCH v9 3/7] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping Dou Liyang
2016-07-25 8:35 ` [PATCH v9 4/7] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Dou Liyang
2016-07-25 8:35 ` [PATCH v9 5/7] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Dou Liyang
2016-07-25 8:35 ` [PATCH v9 6/7] acpi: Provide the mechanism to validate processors in the ACPI tables Dou Liyang
2016-07-25 8:35 ` [PATCH v9 7/7] acpi: Provide the interface to validate the proc_id Dou Liyang
2016-07-25 23:20 ` [PATCH v9 0/7] Make cpuid <-> nodeid mapping persistent Andrew Morton
2016-07-26 0:11 ` Tejun Heo
2016-07-26 0:25 ` Andrew Morton
2016-07-26 1:03 ` Tejun Heo [this message]
2016-07-26 3:59 ` Dou Liyang
2016-07-26 11:53 ` Rafael J. Wysocki
2016-07-27 1:18 ` Dou Liyang
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=20160726010344.GO19588@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chen.tang@easystack.cn \
--cc=cl@linux.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=gongzhaogang@inspur.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mika.j.penttila@gmail.com \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yasu.isimatu@gmail.com \
/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).