On 12/19/2015 05:57 AM, Sumit Gupta wrote:
Hi All, For ARM Linux, during booting first memblock reserves memory regions then bootmem allocator create node, mem_map, page bitmap data and then hands over to buddy. I have been thinking from some time about why we need two different allocators for this. Can we merge both into one(memblock into bootmem) or create a new allocator which can speed up the same thing which is easy to enhance in future. I am not sure about this and whether it's good idea or will it be fruitful. Please suggest and share your opinion. Thank you in advance for your help.
ARM no longer uses bootmem, just memblock (see 84f452b1e8fc73ac0e31254c66e3e2260ce5263d ARM: mm: Remove bootmem code and switch to NO_BOOTMEM). Any bootmem calls just go to mm/nobootmem.c which is a wrapper around memblock for compatibility. Thanks, Laura -- 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
