public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: hugh@veritas.com, linux-kernel@vger.kernel.org,
	mbligh@aracnet.com, wli@holomorphy.com
Subject: Re: 230-objrmap fixes for 2.6.3-mjb2
Date: Sat, 27 Mar 2004 15:24:23 +0100	[thread overview]
Message-ID: <20040327142423.GH9604@dualathlon.random> (raw)
In-Reply-To: <20040326152523.5bfe41db.akpm@osdl.org>

On Fri, Mar 26, 2004 at 03:25:23PM -0800, Andrew Morton wrote:
> Andrea Arcangeli <andrea@suse.de> wrote:
> >
> > On Fri, Mar 26, 2004 at 11:57:23AM +0000, Hugh Dickins wrote:
> > > Andrea's 2.6.5-rc2-aa4 (anon_vma): based on Martin's, but very
> > > likely safe since it does not use find_vma at all in swapout, and
> > > unuse_process downs mmap_sem as Martin's used to before.
> > 
> > Hugh, thanks for the review! I also don't see locking bugs in this area
> > in my tree and I like not to take the page_table_lock during vma
> > manipulations since I don't seem to need it.
> 
> It would be really, really nice if we could clean this crap up.  mmap_sem
> protects the vma tree, i_shared_sem protects the per-address_space vma
> lists and page_table_lock protects the pagetables.
> 
> Does this sound like something we can achieve?

yes, and I already achieved this in my tree, so if you plan to merge my
stuff you don't need to touch it in your tree (so it also avoids me to
reject on stuff I already did).

> (Could page_table_lock then become per-vma?)

I probably could make it per-vma, but it's low prio at this time.

  reply	other threads:[~2004-03-27 14:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  7:09 230-objrmap fixes for 2.6.3-mjb2 Andrea Arcangeli
2004-03-03 10:58 ` Andrew Morton
2004-03-03 15:46   ` Martin J. Bligh
2004-03-03 15:58     ` Dave McCracken
2004-03-03 16:08       ` Christoph Hellwig
2004-03-03 19:04         ` Mike Kravetz
2004-03-04 15:41         ` Rik van Riel
2004-03-04 15:47           ` Christoph Hellwig
2004-03-04 16:21             ` Rik van Riel
2004-03-04 17:03           ` Matt Mackall
2004-03-03 16:57     ` Andrea Arcangeli
2004-03-03 17:07       ` Dave McCracken
2004-03-03 18:39         ` Andrea Arcangeli
2004-03-03 18:44           ` Dave McCracken
2004-03-03 18:51             ` Andrea Arcangeli
2004-03-03 19:01               ` Dave McCracken
2004-03-03 21:05                 ` Andrea Arcangeli
2004-03-03 21:39               ` Martin J. Bligh
2004-03-03 23:16                 ` Andrea Arcangeli
2004-03-03 17:06   ` Andrea Arcangeli
2004-03-03 15:54 ` Martin J. Bligh
2004-03-03 16:14   ` Andrea Arcangeli
2004-03-25 21:45 ` Andrea Arcangeli
2004-03-26 11:57   ` Hugh Dickins
2004-03-26 18:02     ` Andrea Arcangeli
2004-03-26 23:25       ` Andrew Morton
2004-03-27 14:24         ` Andrea Arcangeli [this message]
2004-03-27 15:29         ` 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=20040327142423.GH9604@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=wli@holomorphy.com \
    /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