CONFIG_FORCE_MAX_ZONEORDER settable for all ARM architectures
eric.y.miao at gmail.com
Fri Nov 5 09:59:41 EDT 2010
On Fri, Nov 5, 2010 at 9:41 PM, Daniel Mack <zonque at gmail.com> wrote:
> on a PXA3xx based platform, we want to allocate 8MByte of physically
> contiguous memory for the framebuffer device.
> However, alloc_pages() fails because MAX_ORDER is hard-coded to 11 for
> this architecture.
> Is there any reason why CONFIG_FORCE_MAX_ZONEORDER is constrained to
> ARCH_SHMOBILE in arch/arm/Kconfig? Would a patch to remove this
> limitation be accepted? Or is there any better way to allocate that
> amount and type of memory?
There is actually an on-going discussion of memory region allocator,
be used to solve the allocation of large chunk of physically
contiguous memory by
memory migration at run-time. Some of the ideas were mentioned in a previous
patch of CMA (contiguous memory allocator)? Though I didn't look too much into
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
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
More information about the linux-arm-kernel