From: Sumit Gupta <sumit.g.007@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mm-commits@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Query about merging memblock and bootmem into one new alloc
Date: Sat, 19 Dec 2015 19:10:26 +0530 [thread overview]
Message-ID: <CANDtUregqtqLLa+kFSR+Hqz4dsi5jSQS1=nzUeTaXRE-wTQiyA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
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.
--
Thanks & Regards,
Sumit Gupta
Mob: +91-9717222038
[-- Attachment #2: Type: text/html, Size: 830 bytes --]
reply other threads:[~2015-12-19 13:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANDtUregqtqLLa+kFSR+Hqz4dsi5jSQS1=nzUeTaXRE-wTQiyA@mail.gmail.com' \
--to=sumit.g.007@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox