From: Dave McCracken <dmccr@us.ibm.com>
To: Daniel Phillips <phillips@arcor.de>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Snapshot of shared page tables
Date: Wed, 02 Oct 2002 11:57:26 -0500 [thread overview]
Message-ID: <83240000.1033577846@baldur.austin.ibm.com> (raw)
In-Reply-To: <E17wmit-0001bH-00@starship>
--On Wednesday, October 02, 2002 18:51:41 +0200 Daniel Phillips
<phillips@arcor.de> wrote:
> Interesting, you substituted pte_page_lock(ptepage) for
> mm->page_table_lock. Could you wax poetic about that, please?
Sure. If a pte page is shared, the mm->page_table_lock is not sufficient
to protect the rest of the page fault. Therefore we need a lock at the pte
page level. The mm->page_table_lock is held during the page fault until we
have a valid and locked pte page we're working on, then it's dropped for
the rest of the fault.
Feel free to poke holes in my logic, but I think it's the right locking
model for shared pte pages.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-02 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 14:57 Dave McCracken
2002-10-02 16:51 ` Daniel Phillips
2002-10-02 16:57 ` Dave McCracken [this message]
2002-10-02 17:00 ` Daniel Phillips
2002-10-02 22:39 ` Paul Mackerras
2002-10-02 22:48 ` Dave McCracken
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=83240000.1033577846@baldur.austin.ibm.com \
--to=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=phillips@arcor.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