public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Hellwig <hch@infradead.org>
Cc: Daniel Walker <dwalker@mvista.com>,
	Matthew Wilcox <matthew@wil.cx>,
	linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Announce: Semaphore-Removal tree
Date: Sat, 26 Apr 2008 16:04:34 +0200	[thread overview]
Message-ID: <1209218674.1956.17.camel@lappy> (raw)
In-Reply-To: <20080426134430.GA28205@infradead.org>

On Sat, 2008-04-26 at 09:44 -0400, Christoph Hellwig wrote:
> On Sat, Apr 26, 2008 at 03:39:13PM +0200, Peter Zijlstra wrote:
> > I'm guessing RCU would be a bit more work?
> 
> Actually the whole XFS inode hash is gone now and replaced by a radix tree.
> As soon as nick and your work on the lockless radix trees goes in I'm
> pretty sure Dave will make use of that.

Nick's RCU radix tree is already merged - its just the speculative page
references and the rest of the lockless page-cache that is still
missing.


  reply	other threads:[~2008-04-26 14:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 17:00 Announce: Semaphore-Removal tree Matthew Wilcox
2008-04-25 20:24 ` Daniel Walker
2008-04-25 20:38 ` Daniel Walker
2008-04-25 21:12   ` Christoph Hellwig
2008-04-25 21:22     ` Daniel Walker
2008-04-26  9:30       ` Christoph Hellwig
2008-04-26 13:39         ` Peter Zijlstra
2008-04-26 13:44           ` Christoph Hellwig
2008-04-26 14:04             ` Peter Zijlstra [this message]
2008-04-28  4:59             ` David Chinner
2008-04-26 13:54 ` Stephen Rothwell
2008-04-26 15:59   ` Matthew Wilcox
2008-04-26 16:43     ` Stephen Rothwell
2008-04-28  5:10 ` David Chinner
2008-04-28 12:20   ` Matthew Wilcox
2008-04-29  0:09     ` David Chinner
2008-04-29  2:35       ` Matthew Wilcox
2008-04-29  3:56         ` David Chinner
2008-04-30 10:21           ` Matthew Wilcox
2008-04-30 10:06       ` Matthew Wilcox
2008-04-30 11:01         ` David Chinner

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=1209218674.1956.17.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=dwalker@mvista.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=sfr@canb.auug.org.au \
    /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