From: Andrew Morton <akpm@digeo.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove page_table_lock from vma manipulations
Date: Wed, 04 Jun 2003 15:38:09 -0700 [thread overview]
Message-ID: <3EDE74D1.767C6071@digeo.com> (raw)
In-Reply-To: 133290000.1054765825@baldur.austin.ibm.com
Dave McCracken wrote:
>
> After more careful consideration, I don't see any reasons why
> page_table_lock is necessary for dealing with vmas. I found one spot in
> swapoff, but it was easily changed to mmap_sem.
What keeps the VMA tree consistent when try_to_unmap_one()
runs find_vma()?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove page_table_lock from vma manipulations
Date: Wed, 04 Jun 2003 15:38:09 -0700 [thread overview]
Message-ID: <3EDE74D1.767C6071@digeo.com> (raw)
In-Reply-To: 133290000.1054765825@baldur.austin.ibm.com
Dave McCracken wrote:
>
> After more careful consideration, I don't see any reasons why
> page_table_lock is necessary for dealing with vmas. I found one spot in
> swapoff, but it was easily changed to mmap_sem.
What keeps the VMA tree consistent when try_to_unmap_one()
runs find_vma()?
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-04 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 22:30 [PATCH] Remove page_table_lock from vma manipulations Dave McCracken
2003-06-04 22:37 ` William Lee Irwin III
2003-06-04 22:37 ` William Lee Irwin III
2003-06-04 22:38 ` Andrew Morton [this message]
2003-06-04 22:38 ` Andrew Morton
2003-06-04 22:58 ` Dave McCracken
2003-06-05 16:12 ` Hugh Dickins
2003-06-05 16:12 ` Hugh Dickins
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=3EDE74D1.767C6071@digeo.com \
--to=akpm@digeo.com \
--cc=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.