From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Christoph Lameter <clameter@sgi.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] radix-tree: fix radix_tree_replace_slot
Date: Thu, 24 Aug 2006 12:36:03 +1000 [thread overview]
Message-ID: <44ED1093.3050905@yahoo.com.au> (raw)
In-Reply-To: <1156278317.5622.14.camel@localhost>
Lee Schermerhorn wrote:
> I was waiting to hear from Nick on this, but I understand that he has
> severely injured one hand, restricting his keyboard access for a while.
Yeah sorry Lee, ping times have gone up and throughput down.
This does look like the right fix to me. Thanks very much for tracking
it down. Both these patches are
Acked-by: Nick Piggin <npiggin@suse.de>
BTW. I'll have to do a little rework on the radix tree to get the
lockless pagecache patches working properly after the direct-data
patches (based on review feedback)... that will take me a while :(
In the meantime, RCU radix tree isn't getting any lock-free testing
because everything still takes tree_lock... I wonder if Andrew would
be brave enough to lift the tree_lock from mm/readahead.c ?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-08-24 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 20:25 Lee Schermerhorn
2006-08-22 21:06 ` Christoph Lameter
2006-08-22 21:24 ` Lee Schermerhorn
2006-08-24 2:36 ` Nick Piggin [this message]
2006-08-24 5:05 ` Paul E. McKenney
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=44ED1093.3050905@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=paulmck@us.ibm.com \
/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