[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091217195530.GM9804@basil.fritz.box>
Date: Thu, 17 Dec 2009 20:55:30 +0100
From: Andi Kleen <andi@...stfloor.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: Andi Kleen <andi@...stfloor.org>,
Peter Zijlstra <peterz@...radead.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
"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 Thu, Dec 17, 2009 at 11:08:04AM -0800, Paul E. McKenney wrote:
> On Thu, Dec 17, 2009 at 06:53:39PM +0100, Andi Kleen wrote:
> > > OK, I have to ask...
> > >
> > > Why not just use the already-existing SRCU in this case?
> >
> > You right, SRCU could work.
> >
> > Still needs a lot more work of course.
>
> As discussed with Peter on IRC, I have been idly thinking about how I
> would implement SRCU if I were starting on it today. If you would like
> to see some specific improvements to SRCU, telling me about them would
> greatly increase the probability of my doing something about them. ;-)
I think actual RCU improvements are pretty low on the list for this
one, so far we're not even completely sure how it would all work
on the high level.
mmap_sem is a nasty lock, handlings lots of different things.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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