From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT
Date: Sat, 29 Jul 2006 05:55:23 +0200 [thread overview]
Message-ID: <20060729035523.GA29875@elte.hu> (raw)
In-Reply-To: <20060728194104.GA11622@osiris.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> Hm... how about this one then:
>
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
>
> Introduce ARCH_LOW_ADDRESS_LIMIT which can be set per architecture to
> override the 4GB default limit used by the bootmem allocater within
> __alloc_bootmem_low() and __alloc_bootmem_low_node().
> E.g. s390 needs a 2GB limit instead of 4GB.
>
> Cc: Ingo Molnar <mingo@elte.hu>
Acked-by: Ingo Molnar <mingo@elte.hu>
(although you might get some flak about using an ARCH* define. I'm not
sure what the current upstream policy is - using an #ifndef default
value is the most compact hence sanest thing to do, still it's sometimes
being frowned upon in favor of sprinkling the default value into every
architecture's processor.h. Putting the value into a Kconfig and
combining it with #ifndef might be better.)
Ingo
next prev parent reply other threads:[~2006-07-29 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 13:08 [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT Heiko Carstens
2006-07-28 13:13 ` Ingo Molnar
2006-07-28 14:58 ` Martin Schwidefsky
2006-07-28 19:41 ` Heiko Carstens
2006-07-29 3:55 ` Ingo Molnar [this message]
2006-08-07 5:27 ` Randy.Dunlap
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=20060729035523.GA29875@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox