On Thu, 2011-04-21 at 11:45 -0700, Dave Hansen wrote: > On Thu, 2011-04-21 at 13:33 -0500, Christoph Lameter wrote: > > http://www.linux-mips.org/archives/linux-mips/2008-08/msg00154.html > > > > http://mytechkorner.blogspot.com/2010/12/sparsemem.html > > > > Dave Hansen, Mel: Can you provide us with some help? (Its Easter and so > > the europeans may be off for awhile) > > Yup, for sure. It's also interesting how much code ppc64 removed when > they did this: > > http://lists.ozlabs.org/pipermail/linuxppc64-dev/2005-November/006646.html I looked at converting parisc to sparsemem and there's one problem that none of these cover. How do you set up bootmem? If I look at the examples, they all seem to have enough memory in the first range to allocate from, so there's no problem. On parisc, with discontigmem, we set up all of our ranges as bootmem (we can do this because we effectively have one node per range). Obviously, since sparsemem has a single bitmap for all of the bootmem, we can no longer allocate all of our memory to it (well, without exploding because some of our gaps are gigabytes big). How does everyone cope with this (do you search for your largest range and use that as bootmem or something)? James If -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>