Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT

From: Ingo Molnar
Date: Fri Jul 28 2006 - 23:59:14 EST



* Heiko Carstens <heiko.carstens@xxxxxxxxxx> wrote:

> Hm... how about this one then:
>
> From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
>
> 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@xxxxxxx>

Acked-by: Ingo Molnar <mingo@xxxxxxx>

(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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/