public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Grover <andy.grover@gmail.com>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4level page tables for Linux II
Date: Thu, 14 Oct 2004 18:55:20 -0700	[thread overview]
Message-ID: <c0a09e5c041014185545517031@mail.gmail.com> (raw)
In-Reply-To: <pan.2004.10.14.16.57.23.884792@smurf.noris.de>

On Thu, 14 Oct 2004 18:57:24 +0200, Matthias Urlichs
<smurf@smurf.noris.de> wrote:
> Hi, Andi Kleen wrote:
> 
> > And when you cannot remember the few names for the level you
> > better shouldn't touch VM at all.
> 
> Disagree. Rather strongly in fact.
> 
> It's probably OK if you already know the stuff and have been hacking
> Linux' mm for years already, but if you try to learn how things work by
> actually looking at the code..?
> 
> Just number them. Let pd1 point to pages, pd2 to pd1 entries, and so on.
> (Level zero is the actual pages.)

I happen to agree, but surely this can be addressed at our leisure,
after pml4 is in.

Maybe a good task for the kernel janitors, if we all agree more
sensible names are desirable.

Regards -- Andy

  reply	other threads:[~2004-10-15  1:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13  3:36 4level page tables for Linux II Albert Cahalan
2004-10-13  7:22 ` Andi Kleen
2004-10-13 21:42   ` Albert Cahalan
2004-10-14 16:57   ` Matthias Urlichs
2004-10-15  1:55     ` Andrew Grover [this message]
2004-10-15 13:28       ` Jörn Engel
2004-10-15 13:55         ` Matthias Urlichs
2004-10-15 23:39           ` Jörn Engel
2004-10-17  5:54             ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
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

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=c0a09e5c041014185545517031@mail.gmail.com \
    --to=andy.grover@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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