All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andrea Arcangeli <andrea@novell.com>
Cc: haveblue@us.ibm.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 4level page tables for Linux
Date: Wed, 13 Oct 2004 21:35:58 +0200	[thread overview]
Message-ID: <20041013213558.43b3236c.ak@suse.de> (raw)
In-Reply-To: <20041013184153.GO17849@dualathlon.random>

On Wed, 13 Oct 2004 20:41:53 +0200
Andrea Arcangeli <andrea@novell.com> wrote:


> 
> after you add the 4level, locking will become necessary for the pgd, but
> it's still not needed for the pml4.

Yes, agreed. I did an audit of the generic code and it seems to be ok
regarding the pgd use.


> peraphs we could consider pgd4 instead of pml4. What does "pml" stands
> for?

page mapping level 4 (?) just guessing here.

PML4 is the name AMD and Intel use in their documentation. I don't see 
a particular reason to be different from them.

-Andi

  reply	other threads:[~2004-10-13 19:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 13:59 4level page tables for Linux Andi Kleen
2004-10-12 18:48 ` Dave Hansen
2004-10-12 19:03   ` Andi Kleen
2004-10-12 19:08     ` 4level page tables for Linux II Andi Kleen
2004-10-13 18:41   ` 4level page tables for Linux Andrea Arcangeli
2004-10-13 19:35     ` Andi Kleen [this message]
2004-10-13 20:04       ` Andrea Arcangeli
2004-10-18 17:02         ` Christoph Lameter
2004-10-18 17:21           ` Andi Kleen
2004-10-18 17:38           ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2004-10-13 23:22 Albert Cahalan
2004-10-13 23:51 ` Andrea Arcangeli
2004-10-14  1:15   ` Albert Cahalan
2004-10-14  9:25 linux
2004-10-14 11:15 ` Robin Holt
2004-10-17  2:57 ` H. Peter Anvin

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=20041013213558.43b3236c.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=andrea@novell.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.