From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [RFC] Variable Kernel Page size support
Date: Fri, 13 Oct 2006 00:50:50 +0000 [thread overview]
Message-ID: <000501c6ee61$a11df010$db34030a@amr.corp.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610121730050.22778@schroedinger.engr.sgi.com>
Christoph Lameter wrote on Thursday, October 12, 2006 5:33 PM
> IA64: Variable Kernel Page size support
>
> This patch adds the capability to manage pages of varying sizes for the
> kernel in region 7. This is done by setting special bits in bits 54 to 60.
>
> 54-59 Page size.
>
> If set then the default pagesize of region 7 is overridden on a fault
> and a TLB of the requested size is inserted. This may be used to
> manually control the coverage of a single TLB. A macro SET_TLB_SIZE
> is provide that can be used upon a kernel address to encode the
> desired page size. Code must refer to the address range through
> this address in order to get the desired TLB size.
>
> 60 Page table enable.
This is just getting better and better :-)) nifty!
> If set then a lookup is performed using the region7_pgdir table.
> That table is segmented into 8 section for the varying page
> sizes supported.
What is the reason to anchor these 8 sections with pgdir? Can't we just
extract page size directly from the virtual address? Chop off bit 54 - 60,
that's the physical address, whola. I don't see why it can't be done.
next prev parent reply other threads:[~2006-10-13 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 0:32 [RFC] Variable Kernel Page size support Christoph Lameter
2006-10-13 0:50 ` Chen, Kenneth W [this message]
2006-10-13 0:55 ` Chen, Kenneth W
2006-10-13 1:12 ` Christoph Lameter
2006-10-13 1:28 ` Chen, Kenneth W
2006-10-13 1:38 ` Christoph Lameter
2006-10-13 9:21 ` Robin Holt
2006-10-13 18:03 ` Christoph Lameter
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='000501c6ee61$a11df010$db34030a@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.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