[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50B48D7C.3070706@zytor.com>
Date: Tue, 27 Nov 2012 01:53:00 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Wen Congyang <wency@...fujitsu.com>
CC: Tang Chen <tangchen@...fujitsu.com>, Bob Liu <lliubbo@...il.com>,
akpm@...ux-foundation.org, rob@...dley.net,
isimatu.yasuaki@...fujitsu.com, laijs@...fujitsu.com,
linfeng@...fujitsu.com, jiang.liu@...wei.com, yinghai@...nel.org,
kosaki.motohiro@...fujitsu.com, minchan.kim@...il.com,
mgorman@...e.de, rientjes@...gle.com, rusty@...tcorp.com.au,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-doc@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [PATCH v2 0/5] Add movablecore_map boot option
On 11/27/2012 01:47 AM, Wen Congyang wrote:
> At 11/27/2012 04:49 PM, H. Peter Anvin Wrote:
>> On 11/27/2012 12:29 AM, Tang Chen wrote:
>>> Another approach is like the following:
>>> movable_node = 1,3-5,8
>>> This could set all the memory on the nodes to be movable. And the rest
>>> of memory works as usual. But movablecore_map is more flexible.
>>
>> ... but *much* harder for users, so movable_node is better in most cases.
>
> But numa is initialized very later, and we need the information in SRAT...
>
> Thanks
> Wen Congyang
>
I think you need to deal with it for usability reasons, though...
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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