From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: cl@linux.com, mika.j.penttila@gmail.com, mingo@redhat.com,
akpm@linux-foundation.org, 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,
Tang Chen <tangchen@cn.fujitsu.com>,
Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Subject: Re: [PATCH v8 1/7] x86, memhp, numa: Online memory-less nodes at boot time.
Date: Wed, 20 Jul 2016 09:52:56 +0800 [thread overview]
Message-ID: <dcce26e9-bd9f-e9db-b1c7-6a18271395f2@cn.fujitsu.com> (raw)
In-Reply-To: <20160719185017.GM3078@mtj.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
a?? 2016a1'07ae??20ae?JPY 02:50, Tejun Heo a??e??:
> Hello,
>
> On Tue, Jul 19, 2016 at 03:28:02PM +0800, Dou Liyang wrote:
>> In this series of patches, we are going to construct cpu <-> node mapping
>> for all possible cpus at boot time, which is a 1-1 mapping. It means the
> 1-1 mapping means that each cpu is mapped to its own private node
> which isn't the case. Just call it a persistent mapping?
Yes, each cpu is just in a persistent node.
However, the opposite is not true.
I will modify it.
>
>> cpu will be mapped to the node it belongs to, and will never be changed.
>> If a node has only cpus but no memory, the cpus on it will be mapped to
>> a memory-less node. And the memory-less node should be onlined.
>>
>> This patch allocate pgdats for all memory-less nodes and online them at
>> boot time. Then build zonelists for these nodes. As a result, when cpus
>> on these memory-less nodes try to allocate memory from local node, it
>> will automatically fall back to the proper zones in the zonelists.
> Yeah, I think this is an a lot better approach for memory-less nodes.
>
>> Signed-off-by: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Thanks,
Dou
[-- Attachment #2: Type: text/html, Size: 2559 bytes --]
next prev parent reply other threads:[~2016-07-20 1:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 7:28 [PATCH v8 0/7] Make cpuid <-> nodeid mapping persistent Dou Liyang
2016-07-19 7:28 ` [PATCH v8 1/7] x86, memhp, numa: Online memory-less nodes at boot time Dou Liyang
2016-07-19 18:50 ` Tejun Heo
2016-07-20 1:52 ` Dou Liyang [this message]
2016-07-20 2:28 ` Dou Liyang
2016-07-19 7:28 ` [PATCH v8 2/7] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus " Dou Liyang
2016-07-19 7:28 ` [PATCH v8 3/7] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping Dou Liyang
2016-07-19 7:28 ` [PATCH v8 4/7] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Dou Liyang
2016-07-19 7:28 ` [PATCH v8 5/7] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Dou Liyang
2016-07-19 20:06 ` Rafael J. Wysocki
2016-07-20 1:25 ` Dou Liyang
2016-07-19 7:28 ` [PATCH v8 6/7] Provide the mechanism to validate processors in the ACPI tables Dou Liyang
2016-07-19 7:28 ` [PATCH v8 7/7] Provide the interface to validate the proc_id which they give Dou Liyang
2016-07-19 18:53 ` Tejun Heo
2016-07-20 0:55 ` 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=dcce26e9-bd9f-e9db-b1c7-6a18271395f2@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=chen.tang@easystack.cn \
--cc=cl@linux.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=tangchen@cn.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yasu.isimatu@gmail.com \
--cc=zhugh.fnst@cn.fujitsu.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).