This isn't a "tweak" on ARM as in a user-adjustable value. It needs to
specifically be reduced to prevent things from blowing up.
So, when SA1111-type machines are selected, the max zone order _must_
(no ifs or buts) be set to 9 or below.
> +/* This is the number of free areas per zone to manage, but the max
> + * number determines the maximum order of a page allocation request
> + * as well. */
> +/* Default: 11 */
> +#if defined(ASSABET_NEPONSET0) || defined(SA1100_ADSBITSY) || \
> + defined(SA1100_BADGE4) || defined(SA1100_CONSUS) || \
> + defined(SA1100_GRAPHICSMASTER) || defined(SA1100_JORNADA720) || \
> + defined(ARCH_LUBBOCK) || defined(SA1100_PFS168) || \
> + defined(SA1100_PT_SYSTEM3) || defined(SA1100_XP860)
> +#undef TWEAK_MAX_ORDER
> +#define TWEAK_MAX_ORDER 9
And the reason we have it in the configuration rather than the code is
to get rid of crap like the above.
-- Russell King (email@example.com) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/