From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: CONFIG_FORCE_MAX_ZONEORDER settable for all ARM architectures
Date: Fri, 5 Nov 2010 14:07:16 +0000 [thread overview]
Message-ID: <20101105140716.GC23828@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTikjQhKXgYzczAx70R3JkQ=DoE-xFNux=s6jUeLB@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-11-05 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 13:41 CONFIG_FORCE_MAX_ZONEORDER settable for all ARM architectures Daniel Mack
2010-11-05 13:59 ` Eric Miao
2010-11-05 14:07 ` Russell King - ARM Linux [this message]
2010-11-05 14:14 ` Daniel Mack
2010-11-05 14:01 ` Russell King - ARM Linux
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=20101105140716.GC23828@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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