Re: memblock versus bootmem (relevant for sparc32?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > 
> > Replacing bootmem seems like a bigger task - that will wait.
> 
> will need to move get_free_all_memory_range() and related funcs
> from arch/x86/mm/memblock.c to mm/memblock.c or mm/nobootmem.c

It would be great if you could look at this - then it would be more obvious what is needed
for other archs to support nobootmem.

> 
> replacing bootmem with memblock in arch code should be simple.

This is also my impression after looking at it.

As for sparc32 I will give it a try - but it will take a while as I need to finish
some other stuff first.

	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


[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux