From: Nick Piggin <npiggin@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, paulus@samba.org
Subject: Re: [patch 7/7] powerpc: lockless get_user_pages_fast
Date: Wed, 11 Jun 2008 05:18:22 +0200 [thread overview]
Message-ID: <20080611031822.GA8228@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0806101159110.17798@schroedinger.engr.sgi.com>
On Tue, Jun 10, 2008 at 12:00:48PM -0700, Christoph Lameter wrote:
> On Thu, 5 Jun 2008, npiggin@suse.de wrote:
>
> > Index: linux-2.6/include/linux/mm.h
> > ===================================================================
> > --- linux-2.6.orig/include/linux/mm.h
> > +++ linux-2.6/include/linux/mm.h
> > @@ -244,7 +244,7 @@ static inline int put_page_testzero(stru
> > */
> > static inline int get_page_unless_zero(struct page *page)
> > {
> > - VM_BUG_ON(PageTail(page));
> > + VM_BUG_ON(PageCompound(page));
> > return atomic_inc_not_zero(&page->_count);
> > }
>
> This is reversing the modification to make get_page_unless_zero() usable
> with compound page heads. Will break the slab defrag patchset.
Is the slab defrag patchset in -mm? Because you ignored my comment about
this change that assertions should not be weakened until required by the
actual patchset. I wanted to have these assertions be as strong as
possible for the lockless pagecache patchset.
--
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:[~2008-06-11 3:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 9:43 [patch 0/7] speculative page references, lockless pagecache, lockless gup npiggin
2008-06-05 9:43 ` [patch 1/7] mm: readahead scan lockless npiggin
2008-06-05 9:43 ` [patch 2/7] radix-tree: add gang_lookup_slot, gang_lookup_slot_tag npiggin
2008-06-05 9:43 ` [patch 3/7] mm: speculative page references npiggin
2008-06-06 14:20 ` Peter Zijlstra
2008-06-06 16:26 ` Nick Piggin
2008-06-06 16:27 ` Nick Piggin
2008-06-09 4:48 ` Tim Pepper
2008-06-10 19:08 ` Christoph Lameter
2008-06-11 3:19 ` Nick Piggin
2008-06-05 9:43 ` [patch 4/7] mm: lockless pagecache npiggin
2008-06-05 9:43 ` [patch 5/7] mm: spinlock tree_lock npiggin
2008-06-05 9:43 ` [patch 6/7] powerpc: implement pte_special npiggin
2008-06-06 4:04 ` Benjamin Herrenschmidt
2008-06-05 9:43 ` [patch 7/7] powerpc: lockless get_user_pages_fast npiggin
2008-06-09 8:32 ` Andrew Morton
2008-06-10 3:15 ` Nick Piggin
2008-06-10 19:00 ` Christoph Lameter
2008-06-11 3:18 ` Nick Piggin [this message]
2008-06-11 4:40 ` Christoph Lameter
2008-06-11 4:41 ` Christoph Lameter
2008-06-11 4:49 ` Nick Piggin
2008-06-11 6:06 ` Andrew Morton
2008-06-11 6:24 ` Nick Piggin
2008-06-11 6:50 ` Andrew Morton
2008-06-11 23:20 ` Christoph Lameter
2008-06-11 4:47 ` Nick Piggin
2008-06-05 11:53 ` [patch 0/7] speculative page references, lockless pagecache, lockless gup Nick Piggin
2008-06-05 17:33 ` Linus Torvalds
2008-06-06 0:08 ` Nick Piggin
2008-06-06 21:32 ` 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=20080611031822.GA8228@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulus@samba.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