[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C3349BF.7030104@austin.ibm.com>
Date: Tue, 06 Jul 2010 10:20:31 -0500
From: Nathan Fontenot <nfont@...tin.ibm.com>
To: Dave Hansen <dave@...ux.vnet.ibm.com>
CC: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Greg KH <gregkh@...e.de>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] memory hotplug disable boot option
On 07/01/2010 08:23 AM, Dave Hansen wrote:
>
> I was thinking more along the lines of just taking adjacent sections and
> merging them. We'll need a new "end address" or size file. Maybe
> "end_phys_index" or something similar.
>
> Such a beast would not fix all of the pathological cases, like where
> only every other 16MB section is populated with RAM, but I don't think
> those are very common at all, especially in cases where there's a lot of
> RAM. But, it also has a chance of being relatively backward-compatible.
> In most cases, we may even be able to calculate a new phys_block_size
> where everything fits evenly and be fully backward-compatible with the
> old ABI.
>
Under this scenario were you thinking that all of the memory sections that
reside under this memory block would then be acted upon as a whole. For
example would we allow users to hotplug individual memory sections included
in th block, or would the memory block be acted upon as a whole?
-Nathan
--
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