From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: Andrew Grover <andy.grover@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 4level page tables for Linux II
Date: Sat, 16 Oct 2004 01:39:28 +0200 [thread overview]
Message-ID: <20041015233928.GA15449@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20041015135520.GA25999@kiste>
On Fri, 15 October 2004 15:55:21 +0200, Matthias Urlichs wrote:
>
> Right now, so are the existing names: you have to remember which is which.
That appears to be the problem with any name. Still, my confusion
about which is read(2) and which is write(2) is rare.
> Levels numbered 1..4 are much simpler: you only have to remember that
> the actual pages are level zero.
if and goto is much simpler, compared to while, for, do..while, else,
and whatever slipped my mind right now. Maybe you should target the c
standard next. ;)
> The solution of your typo problem is typechecking in the compiler;
> presumably it'll warn me if I try to store a pgd3 pointer in a pgd2
> entry.
That should help somewhat, agreed. Patches?
Jörn
--
Public Domain - Free as in Beer
General Public - Free as in Speech
BSD License - Free as in Enterprise
Shared Source - Free as in "Work will make you..."
next prev parent reply other threads:[~2004-10-15 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 3:36 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
2004-10-15 13:28 ` Jörn Engel
2004-10-15 13:55 ` Matthias Urlichs
2004-10-15 23:39 ` Jörn Engel [this message]
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=20041015233928.GA15449@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=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
all inboxes | Powered by JetHome®