[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51033186.3000706@zytor.com>
Date: Fri, 25 Jan 2013 17:29:42 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: Tang Chen <tangchen@...fujitsu.com>, jiang.liu@...wei.com,
wujianguo@...wei.com, wency@...fujitsu.com, laijs@...fujitsu.com,
linfeng@...fujitsu.com, yinghai@...nel.org,
isimatu.yasuaki@...fujitsu.com, rob@...dley.net,
kosaki.motohiro@...fujitsu.com, minchan.kim@...il.com,
mgorman@...e.de, rientjes@...gle.com, guz.fnst@...fujitsu.com,
rusty@...tcorp.com.au, lliubbo@...il.com, jaegeuk.hanse@...il.com,
tony.luck@...el.com, glommer@...allels.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 3/3] acpi, memory-hotplug: Support getting hotplug info
from SRAT.
On 01/25/2013 05:12 PM, Andrew Morton wrote:
> On Fri, 25 Jan 2013 17:42:09 +0800
> Tang Chen <tangchen@...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?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists