On Sat, 2011-04-23 at 19:42 +0200, Sam Ravnborg wrote: > Hi Ben, Yinghai, Ingo. > > While doing some sparc related tasks I noticed that sparc64 > uses memblock - whereas sparc32 does not. > > I am aware that memblock was called lmb in the older days and > that sparc64 had lmb support which was converted to memblock support. > > But so far I have failed to find any information on what the benefit > of memblock is and how it compared to for example bootmem. > I can see that x86 no longer uses bootmem - as the only arch. Mostly memblock works earlier and handles both the actual physical memory layout and allocation within that memory. Archs like powerpc still use memblock, then bootmem, then page alloc. x86 eventually removed the bootmem step in the middle, which is a good thing, unfortunately... > But I also noticed that mm/nobootmem.c contains several functions > named bla_x86_bla(). So I continued to be a bit confused. ... as you noticed, this is all quite horrible with x86 junk in generic places etc... and so I haven't yet looked at doing that on powerpc as well (though I'd like to at some stage). > Do there exist any writeup of what memblock is? Other than the code ? :-) It's a very simple region list management which works on two lists, one represents the physical memory in the system and the other represents reserved areas and can be used as an allocator (or to reserve "FW" regions etc...). It initially worked entirely on static arrays (it used to be that way so it can be used very early during boot), but it now grew the ability to re-allocate its own arrays so that it can be used more generically as an allocator instead of bootmem. It's probably slower than bootmem tho, but on the other hand it shouldn't be on any critical path. > Also does it make sense to consider introducing memblock for sparc32. > And if yes - what is the benefit and what does it replace? I will let DaveM reply here :-) > And would it make sense to drop bootmem on sparc64? > > I know - lots of questions! Cheers, Ben. > Sam -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
