From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <npiggin@suse.de>
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: Mon, 12 Nov 2007 12:21:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711121216150.27479@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071111085004.GF19816@wotan.suse.de>
On Sun, 11 Nov 2007, Nick Piggin wrote:
> +static inline int page_freeze_refs(struct page *page, int count)
> +{
> + return likely(atomic_cmpxchg(&page->_count, count, 0) == count);
> +}
> +
> +static inline void page_unfreeze_refs(struct page *page, int count)
> +{
> + VM_BUG_ON(page_count(page) != 0);
> + VM_BUG_ON(count == 0);
> +
> + atomic_set(&page->_count, count);
> +}
Good idea. That avoids another page bit.
> Index: linux-2.6/mm/migrate.c
> ===================================================================
> --- linux-2.6.orig/mm/migrate.c
> +++ linux-2.6/mm/migrate.c
> @@ -294,6 +294,7 @@ out:
> static int migrate_page_move_mapping(struct address_space *mapping,
> struct page *newpage, struct page *page)
> {
> + int expected_count;
> void **pslot;
>
> if (!mapping) {
> @@ -308,12 +309,18 @@ static int migrate_page_move_mapping(str
> pslot = radix_tree_lookup_slot(&mapping->page_tree,
> page_index(page));
>
> - if (page_count(page) != 2 + !!PagePrivate(page) ||
> + expected_count = 2 + !!PagePrivate(page);
> + if (page_count(page) != expected_count ||
> (struct page *)radix_tree_deref_slot(pslot) != page) {
> write_unlock_irq(&mapping->tree_lock);
> return -EAGAIN;
> }
>
> + if (!page_freeze_refs(page, expected_count))
> + write_unlock_irq(&mapping->tree_lock);
> + return -EAGAIN;
> + }
> +
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.
--
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-12 20:21 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 [this message]
2007-11-13 0:35 ` Nick Piggin
2007-11-13 0:37 ` Christoph Lameter
2007-11-13 0:51 ` Nick Piggin
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=Pine.LNX.4.64.0711121216150.27479@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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