[lkml]   [2009]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: + memory-hotplug-alloc-page-from-other-node-in-memory-online.patch added to -mm tree
On Thu, 2 Jul 2009 09:31:04 -0400 (EDT)
Christoph Lameter <> wrote:

> On Thu, 2 Jul 2009, Yasunori Goto wrote:
> > However, I don't enough time for memory hotplug now,
> > and they are just redundant functions now.
> > If someone create new allocator (and unifying bootmem allocator),
> > I'm very glad. :-)
> "Senior"ities all around.... A move like that would require serious
> commitment of time. None of us older developers can take that on it
> seems.
> Do we need to accept that the zone and page metadata are living on another
> node?
I don't think so. Someone should do. I just think I can't do it _now_.
(because I have more things to do for cgroup..)

And, if not node-hotplug, memmap is allocated from local memory if possible.
"We should _never_ allow fallback to other nodes or not" is problem ?
I think we should allow fallback.
About pgdat, zones, I hope they will be on-cache...

Maybe followings are necessary for allocating pgdat/zones from local node
at node-hotplug.

a) Add new tiny functions to alloacate memory from not-initialized area.
allocate pgdat/memmap from here if necessary.
b) leave allocated memory from (a) as PG_reserved at onlining.
c) There will be "not unpluggable" section after (b). We should show this to
d) For removal, we have to keep precise trace of PG_reserved pages.
e) vmemmap removal, which uses large page for vmemmap, is a problem.
edges of section memmap is not aligned to large pages. Then we need
some clever trick to handle this.

Allocationg memmap from its own section was an idea (I love this) but
IBM's 16MB memory section doesn't allow this.


 \ /
  Last update: 2009-07-03 02:01    [W:0.046 / U:0.260 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site