From: Andrea Arcangeli <andrea@novell.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 4level page tables for Linux
Date: Wed, 13 Oct 2004 20:41:53 +0200 [thread overview]
Message-ID: <20041013184153.GO17849@dualathlon.random> (raw)
In-Reply-To: <1097606902.10652.203.camel@localhost>
On Tue, Oct 12, 2004 at 11:48:22AM -0700, Dave Hansen wrote:
> @@ -110,13 +115,18 @@ int install_file_pte(struct mm_struct *m
> unsigned long addr, unsigned long pgoff, pgprot_t prot)
> {
> ...
> + pml4 = pml4_offset(mm, addr);
> +
> + spin_lock(&mm->page_table_lock);
> + pgd = pgd_alloc(mm, pml4, addr);
> + if (!pgd)
> + goto err_unlock;
>
> Locking isn't needed for access to the pml4? This is a wee bit
> different from pgd's and I didn't see any documentation about it
btw, locking isn't needed even for the pgd.
fremap.c is the only one that gets it right:
pgd = pgd_offset(mm, addr);
spin_lock(&mm->page_table_lock);
pmd = pmd_alloc(mm, pgd, addr);
the rest is just overkill but it doesn't hurt in practice.
after you add the 4level, locking will become necessary for the pgd, but
it's still not needed for the pml4.
I'm not very excited about changing the naming, of the pgd/pmd/pte so I
like to keep it like it is now.
peraphs we could consider pgd4 instead of pml4. What does "pml" stands
for?
next prev parent reply other threads:[~2004-10-13 18:42 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 ` Andrea Arcangeli [this message]
2004-10-13 19:35 ` 4level page tables for Linux 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
-- 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=20041013184153.GO17849@dualathlon.random \
--to=andrea@novell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox