From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: large page support for IOP331
Date: Wed, 24 Feb 2010 09:11:11 +0000 [thread overview]
Message-ID: <20100224091111.GA7598@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <9ff69a5d1002240100r708381ceha1ca29f2bd6f18b@mail.gmail.com>
On Wed, Feb 24, 2010 at 02:30:30PM +0530, Prashant Bhole wrote:
> Is there any support of large page for arm architecture?
The short answer is no.
The long answer is that to have 16K pages, it causes bigger problems
with the 2nd level page tables, which from the hardware perspective
are only 256 per L1 entry, but are required to be in unique pages.
next prev parent reply other threads:[~2010-02-24 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 9:00 large page support for IOP331 Prashant Bhole
2010-02-24 9:11 ` Russell King - ARM Linux [this message]
2010-02-24 9:38 ` Prashant Bhole
[not found] <9ff69a5d1002240003g7f615a06q93ef28aea0b30dcf@mail.gmail.com>
2010-02-24 8:12 ` Prashant Bhole
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=20100224091111.GA7598@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;
as well as URLs for NNTP newsgroup(s).