From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: cl@linux.com, Tejun Heo <tj@kernel.org>,
mika.j.penttila@gmail.com, Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"H. Peter Anvin" <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 <len.brown@intel.com>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
chen.tang@easystack.cn, x86@kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [RESEND PATCH v5 0/5] Make cpuid <-> nodeid mapping persistent
Date: Thu, 3 Mar 2016 10:15:17 +0800 [thread overview]
Message-ID: <56D79E35.7030000@cn.fujitsu.com> (raw)
In-Reply-To: <CAJZ5v0j1WMi5qMYoUeto8EbV2XnhZQ1j7eQ3jJtoC7h5dOxxkw@mail.gmail.com>
Hi,
On 03/03/2016 10:08 AM, Rafael J. Wysocki wrote:
> Hi,
>
> On Thu, Mar 3, 2016 at 2:42 AM, Zhu Guihua <zhugh.fnst@cn.fujitsu.com> wrote:
>> [Problem]
>>
>> cpuid <-> nodeid mapping is firstly established at boot time. And workqueue caches
>> the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
>>
>> When doing node online/offline, cpuid <-> nodeid mapping is established/destroyed,
>> which means, cpuid <-> nodeid mapping will change if node hotplug happens. But
>> workqueue does not update wq_numa_possible_cpumask.
>>
> Are there any changes in this version relative to the previous one?
No, there are no changes in this version.
Thanks,
Zhu
>
> Thanks,
> Rafael
>
>
> .
>
--
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>
prev parent reply other threads:[~2016-03-03 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 1:42 Zhu Guihua
2016-03-03 1:42 ` [RESEND PATCH v5 1/5] x86, memhp, numa: Online memory-less nodes at boot time Zhu Guihua
2016-03-03 1:42 ` [RESEND PATCH v5 2/5] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus " Zhu Guihua
2016-03-03 1:42 ` [RESEND PATCH v5 3/5] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping Zhu Guihua
2016-03-03 1:42 ` [RESEND PATCH v5 4/5] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Zhu Guihua
2016-03-03 1:42 ` [RESEND PATCH v5 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Zhu Guihua
2016-03-03 2:11 ` kbuild test robot
2016-03-03 2:18 ` Zhu Guihua
2016-03-03 1:49 ` [RESEND PATCH v5 0/5] Make cpuid <-> nodeid mapping persistent Zhu Guihua
2016-03-03 2:08 ` Rafael J. Wysocki
2016-03-03 2:15 ` Zhu Guihua [this message]
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=56D79E35.7030000@cn.fujitsu.com \
--to=zhugh.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=tglx@linutronix.de \
--cc=tj@kernel.org \
--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