[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080304144406.GA25467@sgi.com>
Date: Tue, 4 Mar 2008 08:44:06 -0600
From: Jack Steiner <steiner@....com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Nick Piggin <npiggin@...e.de>,
Andrea Arcangeli <andrea@...ranet.com>,
akpm@...ux-foundation.org, Robin Holt <holt@....com>,
Avi Kivity <avi@...ranet.com>, Izik Eidus <izike@...ranet.com>,
kvm-devel@...ts.sourceforge.net, general@...ts.openfabrics.org,
Steve Wise <swise@...ngridcomputing.com>,
Roland Dreier <rdreier@...co.com>,
Kanoj Sarcar <kanojsarcar@...oo.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
daniel.blueman@...drics.com, Christoph Lameter <clameter@....com>
Subject: Re: [PATCH] mmu notifiers #v8
On Tue, Mar 04, 2008 at 11:35:32AM +0100, Peter Zijlstra wrote:
>
> On Mon, 2008-03-03 at 13:15 -0600, Jack Steiner wrote:
>
> > I haven't thought about locking requirements for the radix tree. Most accesses
> > would be read-only & updates infrequent. Any chance of an RCU-based radix
> > implementation? Otherwise, don't we add the potential for hot locks/cachelines
> > for threaded applications ???
>
> The current radix tree implementation in the kernel is RCU capable. We
> just don't have many RCU users yet.
Ahhh. You are right. I thought I looked but obviously missed it.
--
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