From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751556AbbLURYJ (ORCPT ); Mon, 21 Dec 2015 12:24:09 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50907 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751314AbbLURYG (ORCPT ); Mon, 21 Dec 2015 12:24:06 -0500 Subject: Re: Query about merging memblock and bootmem into one new alloc To: Sumit Gupta , inux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org References: From: Laura Abbott Message-ID: <567835B4.3090101@redhat.com> Date: Mon, 21 Dec 2015 09:24:04 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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