From: Nick Piggin <nickpiggin@yahoo.com.au>
To: paulmck@us.ibm.com
Cc: Paul McKenney <paul.mckenney@us.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 6/7] mm: lockless pagecache
Date: Fri, 12 Aug 2005 14:04:39 +1000 [thread overview]
Message-ID: <1123819479.5098.16.camel@npiggin-nld.site> (raw)
In-Reply-To: <20050812014924.GQ1300@us.ibm.com>
On Thu, 2005-08-11 at 18:49 -0700, Paul E. McKenney wrote:
> On Thu, Aug 11, 2005 at 10:28:04PM +1000, Nick Piggin wrote:
> > 6/7
> >
> > --
> > SUSE Labs, Novell Inc.
> >
>
> > Use the speculative get_page and the lockless radix tree lookups
> > to introduce lockless page cache lookups (ie. no mapping->tree_lock).
> >
> > The only atomicity changes this should introduce is the use of a
> > non atomic pagevec lookup for truncate, however what atomicity
> > guarantees there were are probably not too useful anyway.
>
> I don't understand the placement of the rcu_read_lock() and
> rcu_read_unlock() calls. Again, possibly because I don't understand
> the overall algorithm yet. And again, search for blank lines.
>
I hope I gave a satisfactory answer to this in the last email. If
not, let me know what I've missed...
Indeed you are right that we could push all the RCU locking down
into the radix tree lookups in the places you mention _if_ we
didn't rely on lookups returning radix tree *slots*.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-08-12 4:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 12:18 [patch 0/7] lockless pagecache 2 Nick Piggin
2005-08-11 12:21 ` [patch 1/7] mm: remove PageReserved rollup Nick Piggin
2005-08-11 12:22 ` [patch 2/7] mm: PG_free flag Nick Piggin
2005-08-11 12:22 ` [patch 3/7] mm: speculative get_page Nick Piggin
2005-08-11 12:25 ` [patch 4/7] radix-tree: lookup_slot Nick Piggin
2005-08-11 12:25 ` [patch 5/7] radix-tree: lockless readside Nick Piggin
2005-08-11 12:28 ` [patch 6/7] mm: lockless pagecache Nick Piggin
2005-08-11 12:28 ` [patch 7/7] mm: spinlock tree_lock Nick Piggin
2005-08-11 13:58 ` [patch 6/7] mm: lockless pagecache Pekka Enberg
2005-08-11 14:06 ` Nick Piggin
2005-08-12 1:49 ` Paul E. McKenney
2005-08-12 4:04 ` Nick Piggin [this message]
2005-08-12 1:37 ` [patch 5/7] radix-tree: lockless readside Paul E. McKenney
2005-08-12 3:59 ` Nick Piggin
2005-08-12 4:38 ` Nick Piggin
2005-08-12 7:53 ` Nick Piggin
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=1123819479.5098.16.camel@npiggin-nld.site \
--to=nickpiggin@yahoo.com.au \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.mckenney@us.ibm.com \
--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
all inboxes | Powered by JetHome®