From: Nick Piggin <npiggin@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Hugh Dickins <hugh@veritas.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch 3/6] mm: speculative get page
Date: Tue, 13 Nov 2007 01:51:43 +0100 [thread overview]
Message-ID: <20071113005143.GF30650@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0711121636170.29328@schroedinger.engr.sgi.com>
On Mon, Nov 12, 2007 at 04:37:28PM -0800, Christoph Lameter wrote:
> On Tue, 13 Nov 2007, Nick Piggin wrote:
>
> > > Good idea. That avoids another page bit.
> >
> > Yeah, it's Hugh's good idea. It avoids smp_rmb() in the find_get_page
> > path as well, which will be helpful at least for things like powerpc
> > and ia64, if not x86. At one single atomic operation to lookup and take
> > a reference on a pagecache page, I think it is approaching the fastest
> > possible implementation ;)
>
> Well I hope all locations that do get_page_unless_zero are aware that a
> failure does not mean that the page is being freed.
Often it does mean the page will be freed soon anyway, so it fits quite well.
But no, nothing assumes the page will be freed. It is hard to imagine the use
of such knowledge would be (outside the page allocator).
You can't use it to assume the page is going to be free at any point T+now,
nor can you assume the pagecache coordinate which used to hold the page is
empty.
> > > Looks okay but I think you could remove the earlier performance check. We
> > > already modified the page struct by obtaining the page lock so we hold it
> > > exclusively. And the failure rate here is typicalyvery low.
> >
> > It's up to you. Honestly, I don't have good test facilities for page
> > migration. If it's all the same to you, do you mind if we leave it like
> > this, and then you can change it in future?
>
> Ok. Lee will likely get to that ;-).
OK good, thanks ;)
--
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:[~2007-11-13 0:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 8:45 [patch 0/6] lockless pagecache Nick Piggin
2007-11-11 8:47 ` [patch 1/6] mm: readahead scan lockless Nick Piggin
2007-11-11 8:49 ` [patch 2/6] radix-tree: gang_lookup_slot Nick Piggin
2007-11-11 8:50 ` [patch 3/6] mm: speculative get page Nick Piggin
2007-11-12 20:21 ` Christoph Lameter
2007-11-13 0:35 ` Nick Piggin
2007-11-13 0:37 ` Christoph Lameter
2007-11-13 0:51 ` Nick Piggin [this message]
2007-11-11 8:51 ` [patch 4/6] mm: lockless pagecache lookups Nick Piggin
2007-11-11 8:51 ` [patch 5/6] mm: spinlock tree_lock Nick Piggin
2007-11-11 8:52 ` [patch 6/6] mm: speculative refcount debug Nick Piggin
2007-11-17 9:48 ` [patch 0/6] lockless pagecache Peter Zijlstra
2007-11-17 20:16 ` Hugh Dickins
2007-11-19 22:58 ` Nick Piggin
2008-01-09 15:45 ` Peter Zijlstra
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=20071113005143.GF30650@wotan.suse.de \
--to=npiggin@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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