linux-kernel - Re: + memory-hotplug-alloc-page-from-other-node-in-memory-online.patch added to -mm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 1 Jul 2009 13:22:33 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	yakui <yakui.zhao@...el.com>
cc:	"Li, Shaohua" <shaohua.li@...el.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"mel@....ul.ie" <mel@....ul.ie>
Subject: Re: + memory-hotplug-alloc-page-from-other-node-in-memory-online.patch
 added to -mm tree

On Wed, 1 Jul 2009, yakui wrote:

> If we can't allocate memory from other node when there is no memory on
> this node, we will have to do something like the bootmem allocator.
> After the memory page is added to the system memory, we will have to
> free the memory space used by the memory allocator. At the same time we
> will have to assure that the hot-plugged memory exists physically.

The bootmem allocator must stick around it seems. Its more like a node
bootstrap allocator then.

Maybe we can generalize that. The bootstrap allocator may only need to be
able boot one node (which simplifies design). During system bringup only
the boot node is brought up.

Then the other nodes are hotplugged later all in turn using the bootstrap
allocator for their node setup?

There are a couple of things where one would want to spread out memory
across the nodes at boot time. How would node hotplugging handle that
situation?
--
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/