[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50F85ED5.3010003@jp.fujitsu.com>
Date: Thu, 17 Jan 2013 15:28:05 -0500
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: tony.luck@...el.com
CC: hpa@...or.com, isimatu.yasuaki@...fujitsu.com,
akpm@...ux-foundation.org, tangchen@...fujitsu.com,
jiang.liu@...wei.com, wujianguo@...wei.com, wency@...fujitsu.com,
laijs@...fujitsu.com, linfeng@...fujitsu.com, yinghai@...nel.org,
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, glommer@...allels.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
On 1/17/2013 11:30 AM, Luck, Tony wrote:
>> 2. If the user *does* care which nodes are movable, then the user needs
>> to be able to specify that *in a way that makes sense to the user*.
>> This may mean involving the DMI information as well as SRAT in order to
>> get "silk screen" type information out.
>
> One reason they might care would be which I/O devices are connected
> to each node. DMI might be a good way to get an invariant name for the
> node, but they might also want to specify in terms of what they actually
> want. E.g. "eth0 and eth4 are a redundant bonded pair of NICs - don't
> mark both these nodes as removable". Though this is almost certainly not
> a job for kernel options, but for some user configuration tool that would
> spit out the DMI names.
I agree DMI parsing should be done in userland if we really need DMI parsing.
--
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