From: Tang Chen <tangchen@cn.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jiang.liu@huawei.com, wujianguo@huawei.com, wency@cn.fujitsu.com,
laijs@cn.fujitsu.com, linfeng@cn.fujitsu.com, yinghai@kernel.org,
isimatu.yasuaki@jp.fujitsu.com, rob@landley.net,
kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com,
mgorman@suse.de, rientjes@google.com, guz.fnst@cn.fujitsu.com,
rusty@rustcorp.com.au, lliubbo@gmail.com,
jaegeuk.hanse@gmail.com, tony.luck@intel.com,
glommer@parallels.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT.
Date: Mon, 28 Jan 2013 10:07:07 +0800 [thread overview]
Message-ID: <5105DD4B.9020901@cn.fujitsu.com> (raw)
In-Reply-To: <51033186.3000706@zytor.com>
On 01/26/2013 09:29 AM, H. Peter Anvin wrote:
> On 01/25/2013 05:12 PM, Andrew Morton wrote:
>> On Fri, 25 Jan 2013 17:42:09 +0800
>> Tang Chen<tangchen@cn.fujitsu.com> wrote:
>>
>>> NOTE: Using this way will cause NUMA performance down because the whole node
>>> will be set as ZONE_MOVABLE, and kernel cannot use memory on it.
>>> If users don't want to lose NUMA performance, just don't use it.
>>
>> I agree with this, but it means that nobody will test any of your new code.
>>
>> To get improved testing coverage, can you think of any temporary
>> testing-only patch which will cause testers to exercise the
>> memory-hotplug changes?
>>
>
> There is another problem: if ALL the nodes in the system support
> hotpluggable memory, what happens?
>
Hi HPA,
I think I missed this case. If all the memory is hotpluggable, and user
specified
movablemem_map=acpi, all the memory could be set as movable, and the
kernel will
fail to start.
I will post a patch to fix it. How about always keep node0 unhotpluggable ?
Thanks. :)
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Tang Chen <tangchen@cn.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jiang.liu@huawei.com, wujianguo@huawei.com, wency@cn.fujitsu.com,
laijs@cn.fujitsu.com, linfeng@cn.fujitsu.com, yinghai@kernel.org,
isimatu.yasuaki@jp.fujitsu.com, rob@landley.net,
kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com,
mgorman@suse.de, rientjes@google.com, guz.fnst@cn.fujitsu.com,
rusty@rustcorp.com.au, lliubbo@gmail.com,
jaegeuk.hanse@gmail.com, tony.luck@intel.com,
glommer@parallels.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT.
Date: Mon, 28 Jan 2013 10:07:07 +0800 [thread overview]
Message-ID: <5105DD4B.9020901@cn.fujitsu.com> (raw)
In-Reply-To: <51033186.3000706@zytor.com>
On 01/26/2013 09:29 AM, H. Peter Anvin wrote:
> On 01/25/2013 05:12 PM, Andrew Morton wrote:
>> On Fri, 25 Jan 2013 17:42:09 +0800
>> Tang Chen<tangchen@cn.fujitsu.com> wrote:
>>
>>> NOTE: Using this way will cause NUMA performance down because the whole node
>>> will be set as ZONE_MOVABLE, and kernel cannot use memory on it.
>>> If users don't want to lose NUMA performance, just don't use it.
>>
>> I agree with this, but it means that nobody will test any of your new code.
>>
>> To get improved testing coverage, can you think of any temporary
>> testing-only patch which will cause testers to exercise the
>> memory-hotplug changes?
>>
>
> There is another problem: if ALL the nodes in the system support
> hotpluggable memory, what happens?
>
Hi HPA,
I think I missed this case. If all the memory is hotpluggable, and user
specified
movablemem_map=acpi, all the memory could be set as movable, and the
kernel will
fail to start.
I will post a patch to fix it. How about always keep node0 unhotpluggable ?
Thanks. :)
next prev parent reply other threads:[~2013-01-28 2:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 9:42 [PATCH 0/3] Support SRAT for movablemem_map boot option Tang Chen
2013-01-25 9:42 ` Tang Chen
2013-01-25 9:42 ` [PATCH 1/3] acpi, memory-hotplug: Parse SRAT before memblock is ready Tang Chen
2013-01-25 9:42 ` Tang Chen
2013-01-25 9:42 ` [PATCH 2/3] acpi, memory-hotplug: Extend movablemem_map ranges to the end of node Tang Chen
2013-01-25 9:42 ` Tang Chen
2013-01-26 0:36 ` Andrew Morton
2013-01-26 0:36 ` Andrew Morton
2013-01-28 1:53 ` Tang Chen
2013-01-28 1:53 ` Tang Chen
2013-01-25 9:42 ` [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info from SRAT Tang Chen
2013-01-25 9:42 ` Tang Chen
2013-01-26 0:40 ` Andrew Morton
2013-01-26 0:40 ` Andrew Morton
2013-01-26 1:12 ` Andrew Morton
2013-01-26 1:12 ` Andrew Morton
2013-01-26 1:29 ` H. Peter Anvin
2013-01-26 1:29 ` H. Peter Anvin
2013-01-28 2:07 ` Tang Chen [this message]
2013-01-28 2:07 ` Tang Chen
2013-01-28 17:45 ` Luck, Tony
2013-01-28 17:45 ` Luck, Tony
2013-01-29 6:43 ` Tang Chen
2013-01-29 18:38 ` Luck, Tony
2013-01-29 18:40 ` H. Peter Anvin
2013-01-28 9:15 ` Tang Chen
2013-01-28 9:15 ` Tang Chen
2013-02-04 23:26 ` Andrew Morton
2013-02-04 23:26 ` Andrew Morton
2013-02-06 2:20 ` Tang Chen
2013-02-06 2:20 ` Tang Chen
2013-02-06 21:54 ` Andrew Morton
2013-02-06 21:54 ` Andrew Morton
2013-02-07 6:22 ` Tang Chen
2013-02-07 6:22 ` Tang Chen
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=5105DD4B.9020901@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jaegeuk.hanse@gmail.com \
--cc=jiang.liu@huawei.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linfeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=tony.luck@intel.com \
--cc=wency@cn.fujitsu.com \
--cc=wujianguo@huawei.com \
--cc=yinghai@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.