From: David Miller <davem@davemloft.net>
To: hannes@cmpxchg.org
Cc: akpm@linux-foundation.org, yinghai@kernel.org, x86@kernel.org,
linux-arch@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: further plans on bootmem, was: Re: - bootmem-avoid-dma32-zone-by-default.patch removed from -mm tree
Date: Tue, 09 Mar 2010 23:16:35 -0800 (PST) [thread overview]
Message-ID: <20100309.231635.199019630.davem@davemloft.net> (raw)
In-Reply-To: <20100310000121.GA9985@cmpxchg.org>
From: Johannes Weiner <hannes@cmpxchg.org>
Date: Wed, 10 Mar 2010 01:01:21 +0100
> I also found it weird that it makes x86 skip an allocator level that all
> the other architectures are using, and replaces it with 'generic' code that
> nobody but x86 is using (sparc, powerpc, sh and microblaze appear to have
> lib/lmb.c at this stage and for this purpose? lmb was also suggested by
> benh [4] but I have to admit I do not understand Yinghai's response to it).
It kind of irked me that lmb was passed over for whatever vague reason
was given.
It works fine with memory hotplug on powerpc, so a lack of hotplug
support can't be an argument for not using it.
But hey, having yet another early memory allocator instead of making
one of the existing ones do what you want, that's fine right?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-03-10 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201003091940.o29Je4Iq000754@imap1.linux-foundation.org>
[not found] ` <4B96B923.7020805@kernel.org>
[not found] ` <20100309134902.171ba2ae.akpm@linux-foundation.org>
2010-03-10 0:01 ` further plans on bootmem, was: Re: - bootmem-avoid-dma32-zone-by-default.patch removed from -mm tree Johannes Weiner
2010-03-10 0:06 ` Yinghai Lu
2010-03-10 7:16 ` David Miller [this message]
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=20100309.231635.199019630.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-arch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=x86@kernel.org \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).