On 01/29/2013 10:38 AM, Luck, Tony wrote: >>> Node 0 (or more specifically the node that contains memory<4GB) will be >>> full of BIOS reserved holes in the memory map. > >> One thing I'm not sure, is memory<4GB always on node 0 ? >> On my box, it is on node 0. > > I think in practice the <4GB memory will be on node 0 ... but it all depends > on how Linux decides to number the nodes ... which in turn depends on the > order of entries in various BIOS tables. So it is theoretically possible that > we'd end up with some system on which the low memory is on some other > node. But it might require stranger than usual BIOS. > > Summary: coding "node == 0" is almost 100% certain to be right - except > on some pathological systems. So code for node==0 and if we ever see > a pathological machine - we can either point and laugh at the BIOS people > that set that up - or possibly fix our code. > We also probably need to weld down the memory that the kernel static areas occupy and where we have allocated memory during boot time. In particular, memory that you want to be movable MUST NOT have boot-time kernel allocations, and it becomes critical to enforce that, lest you pull memory that you thought was safe and crash the system. -hpa -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>