[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091216201218.42ff7f05.kamezawa.hiroyu@jp.fujitsu.com>
Date: Wed, 16 Dec 2009 20:12:18 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>, cl@...ux-foundation.org,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mingo@...e.hu" <mingo@...e.hu>, minchan.kim@...il.com
Subject: Re: [mm][RFC][PATCH 0/11] mm accessor updates.
On Wed, 16 Dec 2009 11:49:51 +0100
Andi Kleen <andi@...stfloor.org> wrote:
> On Wed, Dec 16, 2009 at 07:31:09PM +0900, KAMEZAWA Hiroyuki wrote:
> > On Wed, 16 Dec 2009 11:28:06 +0100
> > Andi Kleen <andi@...stfloor.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.)
>
> I suspect you would just need to change them again then.
>
Do you have alternative recommendation rather than wrapping all accesses by
special functions ?
Thanks,
-Kame
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists