On Tue, 2010-03-30 at 09:32 +1100, Michael Ellerman wrote: > I _suggest_ that if we want to avoid affecting existing lmb users, then > the checking logic should go into the existing API, but be #ifdef'ed for > now - eg. CONFIG_DYNAMIC_LMB or something. That way you avoid affecting > existing users (more or less), but you don't add a new API that you then > have to remove later. > > Having said that I don't think it really does affect existing users that > much. We still have the statically defined region arrays, and they're > still the same size, so sparc and powerpc should never need to resize, > except on machines where we currently run out of space in the array > anyway. We'll want the dynamic sizing if we switch bootmem to lmb (though last I looked, that still needs sparsemem to be fixed as well as it still uses bootmem). There's also some interest on ARM side I've heard. I still have my evil plan to turn it into lists anyways, but we'll see how that goes later. In any case, the doubling ability does the job for now and yes, it should definitely be part of the core. LMB should be able to use it's own storage to do the doubling. IE. Always guarantee that you have at least 1 or 2 free entries in the table, if you're going past that threshold, then use the remaining entry to allocate a new table. Easy :-) Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
