From: Arnd Bergmann <arnd@arndb.de>
To: Laura Abbott <labbott@redhat.com>
Cc: 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 23:01:01 +0100 [thread overview]
Message-ID: <201512212301.02148.arnd@arndb.de> (raw)
In-Reply-To: <567835B4.3090101@redhat.com>
On Monday 21 December 2015, Laura Abbott wrote:
> 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.
It seems the same is true on arc, arm64, powerpc, s390, sparc, tile and x86,
and we'd ideally move all others the same way.
Almost all uses of the bootmem interfaces are in architectures specific code
these days, the only exceptions I could find at all are alloc_bootmem_pages
in drivers/xen/swiotlb-xen.c, and alloc_bootmem in drivers/macintosh/smu.c
and init/main.c.
I don't know how the effort to remove bootmem is progressing, but I guess
we could avoid adding new users if we move the existing implementation into
the architectures that still use it, remove the interfaces not used by
those architectures and rename the other ones to have a prefix identifying
the architecture.
Arnd
next prev parent reply other threads:[~2015-12-21 22:01 UTC|newest]
Thread overview: 6+ 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
2015-12-21 22:01 ` Arnd Bergmann [this message]
2015-12-22 9:47 ` Sam Ravnborg
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=201512212301.02148.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=inux-mm@kvack.org \
--cc=labbott@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).