Date: Wed, 16 Dec 2009 19:31:09 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
       "linux-mm@kvack.org" <linux-mm@kvack.org>, cl@linux-foundation.org,
       "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
       "mingo@elte.hu" <mingo@elte.hu>, minchan.kim@gmail.com
Subject: Re: [mm][RFC][PATCH 0/11] mm accessor updates.
Message-Id: <20091216193109.778b881b.kamezawa.hiroyu@jp.fujitsu.com>
In-Reply-To: <20091216102806.GC15031@basil.fritz.box>
References: <20091216120011.3eecfe79.kamezawa.hiroyu@jp.fujitsu.com>
	<20091216101107.GA15031@basil.fritz.box>
	<20091216191312.f4655dac.kamezawa.hiroyu@jp.fujitsu.com>
	<20091216102806.GC15031@basil.fritz.box>
Organization: FUJITSU Co. LTD.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1121
Lines: 31

On Wed, 16 Dec 2009 11:28:06 +0100
Andi Kleen <andi@firstfloor.org> wrote:

> > > Also the patches didn't fare too well in testing unfortunately.
> > > 
> > > I suspect we'll rather need multiple locks split per address
> > > space range.
> > 
> > This set doesn't include any changes of the logic. Just replace all mmap_sem.
> > I think this is good start point (for introducing another logic etc..)
> 
> The problem is that for range locking simple wrapping the locks
> in macros is not enough. You need more changes.
> 
maybe. but removing scatterred mmap_sem from codes is the first thing to do.
I think this removing itself will take 3 month or a half year.
(So, I didn't remove mmap_sem and leave it as it is.)

The problem of range locking is more than mmap_sem, anyway. I don't think
it's possible easily.

But ok, if no one welcome this, I stop this.

Thanks,
-Kame

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/