From: Michal Hocko <mhocko@kernel.org>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Rob Herring <robh@kernel.org>,
linux-mm@kvack.org, hannes@cmpxchg.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: why do we still need bootmem allocator?
Date: Wed, 27 Jun 2018 12:40:44 +0200 [thread overview]
Message-ID: <20180627104044.GJ32348@dhcp22.suse.cz> (raw)
In-Reply-To: <20180627101144.GC4291@rapoport-lnx>
On Wed 27-06-18 13:11:44, Mike Rapoport wrote:
> On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko <mhocko@kernel.org> wrote:
> > >
> > > Hi,
> > > I am wondering why do we still keep mm/bootmem.c when most architectures
> > > already moved to nobootmem. Is there any fundamental reason why others
> > > cannot or this is just a matter of work?
> >
> > Just because no one has done the work. I did a couple of arches
> > recently (sh, microblaze, and h8300) mainly because I broke them with
> > some DT changes.
>
> I have a patch for alpha nearly ready.
Cool!
> That leaves m68k and ia64
I will not get to those anytime soon (say a week or two) but I have that
close on top of my todo list.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-06-27 10:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 14:07 why do we still need bootmem allocator? Michal Hocko
2018-06-25 16:09 ` Rob Herring
2018-06-25 18:03 ` Michal Hocko
2018-06-27 10:11 ` Mike Rapoport
2018-06-27 10:40 ` Michal Hocko [this message]
2018-06-27 13:58 ` Rob Herring
2018-06-27 13:58 ` Rob Herring
2018-06-27 15:58 ` Mike Rapoport
2018-06-27 15:58 ` Mike Rapoport
2018-06-27 11:26 ` Mike Rapoport
2018-06-27 13:33 ` Rob Herring
2018-06-27 13:33 ` Rob Herring
2018-06-27 16:02 ` Mike Rapoport
2018-06-27 16:02 ` Mike Rapoport
2018-07-01 12:22 ` h8300: BUG: Bad page state in process swapper (was: Re: why do we still need bootmem allocator?) Mike Rapoport
2018-07-01 12:22 ` Mike Rapoport
2018-07-02 6:09 ` Yoshinori Sato
2018-07-02 6:09 ` Yoshinori Sato
2018-07-12 14:40 ` Yoshinori Sato
2018-07-12 14:40 ` Yoshinori Sato
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=20180627104044.GJ32348@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=robh@kernel.org \
--cc=rppt@linux.vnet.ibm.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.