public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Sandeep Kumar <sandeepksinha@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: PAE and PSE ??
Date: Mon, 23 Oct 2006 12:13:46 +0200	[thread overview]
Message-ID: <200610231213.47232.rjw@sisk.pl> (raw)
In-Reply-To: <453C00B7.3040909@zytor.com>

On Monday, 23 October 2006 01:37, H. Peter Anvin wrote:
> Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Sunday, 22 October 2006 08:29, Sandeep Kumar wrote:
> >> Hi all,
> >> I have read in UTLK by bovet that the linux kernel does not uses the
> >> PSE bit on an x86
> >> machine. Then how come we have the hugetlbfs, which provides support
> >> for 4MB pages ?
> > 
> > AFAIK, PSE is only used when PAE is not set and then it enables the 4 MB
> > pages.  If PAE is set, the 4 MB pages are impossible because there are only
> > 512 entries per page table, but 2 MB pages can be used instead (and you don't
> > need to set PSE to use them).
> > 
> 
> You're wrong.
> 
> PSE refers to 4 MB pages when PAE is not used, and 2 MB pages when PAE 
> is used.
> 
> In theory, you could have PAE without PSE, which would only support 4K 
> pages.

Well, "AMD64 Architecture Programmer’s Manual" says the following:

The choice of 2 Mbyte or 4 Mbyte as the large physical-page size
depends on the value of CR4.PSE and CR4.PAE, as follows:
- If physical-address extensions are enabled (CR4.PAE=1), the
   large physical-page size is 2 Mbytes, regardless of the value
   of CR4.PSE.
- If physical-address extensions are disabled (CR4.PAE=0)
   and CR4.PSE=1, the large physical-page size is 4 Mbytes.
- If both CR4.PAE=0 and CR4.PSE=0, the only available page
   size is 4 Kbytes.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

  reply	other threads:[~2006-10-23 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22  6:29 PAE and PSE ?? Sandeep Kumar
2006-10-22 10:15 ` Rafael J. Wysocki
2006-10-22 23:37   ` H. Peter Anvin
2006-10-23 10:13     ` Rafael J. Wysocki [this message]
2006-10-23 14:10       ` H. Peter Anvin
2006-10-23 14:14         ` Rafael J. Wysocki

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=200610231213.47232.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeepksinha@gmail.com \
    /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