CONFIG_FORCE_MAX_ZONEORDER settable for all ARM architectures

Daniel Mack zonque at
Fri Nov 5 10:14:32 EDT 2010

On 11/05/2010 10:07 AM, Russell King - ARM Linux wrote:
> On Fri, Nov 05, 2010 at 09:59:41PM +0800, Eric Miao wrote:
>> However, I'm not really sure about how the size of the memory region is chosen
>> and if the MAX_ORDER issue can be solved as well. So I guess before that
>> happens in mainline, would be acceptable to adjust MAX_ZONEORDER in a
>> hackish way.
> Even if you increase MAX_ZONEORDER, the chances of being able to allocate
> such a large page at runtime will be fairly low due to fragmentation.
> It's something the normal page allocator has never been very good with.

Well, for us, this does work when we increase this number to 12, and as
we build the pxafb statically into the kernel, I would expect the memory
fragmentation situation to be deterministic at each boot. I agree we
couldn't rely on this when loading the driver as module at some later point.


More information about the linux-arm-kernel mailing list