From: Laura Abbott <labbott@redhat.com>
To: Sumit Gupta <sumit.g.007@gmail.com>,
inux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: Query about merging memblock and bootmem into one new alloc
Date: Mon, 21 Dec 2015 09:24:04 -0800 [thread overview]
Message-ID: <567835B4.3090101@redhat.com> (raw)
In-Reply-To: <CANDtUrciap2iHDWpB4SWwACJaUPaLRP4nFb9u9j1=iCJTiuK8Q@mail.gmail.com>
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
next prev parent reply other threads:[~2015-12-21 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 13:57 Query about merging memblock and bootmem into one new alloc Sumit Gupta
2015-12-21 17:24 ` Laura Abbott [this message]
2015-12-21 22:01 ` Arnd Bergmann
2015-12-22 9:47 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2015-12-19 13:40 Sumit Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=567835B4.3090101@redhat.com \
--to=labbott@redhat.com \
--cc=inux-mm@kvack.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.g.007@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.