public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: Andrea Arcangeli <andrea@novell.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>, ak@suse.de
Subject: Re: 4level page tables for Linux
Date: 13 Oct 2004 21:15:43 -0400	[thread overview]
Message-ID: <1097716542.2673.11007.camel@cube> (raw)
In-Reply-To: <20041013235118.GR17849@dualathlon.random>

On Wed, 2004-10-13 at 19:51, Andrea Arcangeli wrote:
> On Wed, Oct 13, 2004 at 07:22:15PM -0400, Albert Cahalan wrote:
> > I'd number going toward the page, because that's
> > the order in which these things get walked.
> 
> I'd call the pml level 1 too, but in the specs is level 4.  So sticking
> the specs numbering is going to generate less confusion. Otherwise when
> we speak with somebody with hardware knowledge we say level 4 and he
> understand the specs's level 1. I recall it already happened to me once ;).

While x86_64 will be by far the most popular arch,
this is a matter for the generic code.

Perhaps "4" should be avoided: 0,1,2,3



  reply	other threads:[~2004-10-14  1:22 UTC|newest]

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

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=1097716542.2673.11007.camel@cube \
    --to=albert@users.sf.net \
    --cc=ak@suse.de \
    --cc=andrea@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox