public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 4level page tables for Linux II
Date: 13 Oct 2004 17:42:55 -0400	[thread overview]
Message-ID: <1097703775.2673.10779.camel@cube> (raw)
In-Reply-To: <20041013092221.471f7232.ak@suse.de>

On Wed, 2004-10-13 at 03:22, Andi Kleen wrote:
> On 12 Oct 2004 23:36:40 -0400
> Albert Cahalan <albert@users.sf.net> wrote:
> 
> > Hmmm...
> > 
> > pml4, pgd, pmd, pte  (kernel names)
> > PML4E, PDPE, PDE, PTE   (AMD hardware names)
> 
> No actually a PML4E is a PML4 _E_ntry in the AMD/Intel docs.
> PML4 is the official name for the fourth level page.
> 
> > It's kind of a mess, isn't it? It was bad enough
> > with the "pmd" (page middle directory, ugh) being
> > some random invention and everything being generally
> > in conflict with real hardware naming. Now you've
> > come up with a fourth name.
> > 
> > Notice that you've resorted to using a number.
> 
> I just followed AMD.
> 
> > Why not do that for the others too? It would
> > bring some order to this ever-growing collection
> > of arbitrary names. Like this:
> 
> I don't think it makes sense to break code unnecessarily.
> 
> And when you cannot remember the few names for the level you 
> better shouldn't touch VM at all.

One of the reasons that Linux is so hackable is that
crummy names get changed. Here too, the old names are bad.

An old example: we use copy_from_user now, not copy_fromfs.
Don't you agree that this is an improvement? It broke code
unnecessarily, but Linus did it anyway. Linux would be a
lot less readable if it had screwy names everywhere.

Perhaps you shouldn't touch kernel code if you can't
remember that copy_fromfs is unrelated to fs code.
Still, why make things difficult? The less effort you
waste remembering stupid names, the more you can spare
for writing great code.



  reply	other threads:[~2004-10-13 21:49 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 [this message]
2004-10-14 16:57   ` Matthias Urlichs
2004-10-15  1:55     ` Andrew Grover
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=1097703775.2673.10779.camel@cube \
    --to=albert@users.sf.net \
    --cc=ak@suse.de \
    --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