From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Nick Piggin <npiggin@suse.de>, Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@osdl.org>, Andy Whitcroft <apw@shadowen.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] mm: speculative get_page
Date: Tue, 01 Aug 2006 10:55:29 -0500 [thread overview]
Message-ID: <1154447729.10401.16.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <20060801193203.GA191@oleg>
On Tue, 2006-08-01 at 23:32 +0400, Oleg Nesterov wrote:
> Nick Piggin wrote:
> >
> > --- linux-2.6.orig/mm/vmscan.c
> > +++ linux-2.6/mm/vmscan.c
> > @@ -380,6 +380,8 @@ int remove_mapping(struct address_space
> > if (!mapping)
> > return 0; /* truncate got there first */
> >
> > + SetPageNoNewRefs(page);
> > + smp_wmb();
> > write_lock_irq(&mapping->tree_lock);
> >
>
> Is it enough?
>
> PG_nonewrefs could be already set by another add_to_page_cache()/remove_mapping(),
> and it will be cleared when we take ->tree_lock.
Isn't the page locked when calling remove_mapping()? It looks like
SetPageNoNewRefs & ClearPageNoNewRefs are called in safe places. Either
the page is locked, or it's newly allocated. I could have missed
something, though.
> For example:
>
> CPU_0 CPU_1 CPU_3
>
> add_to_page_cache:
>
> SetPageNoNewRefs();
> write_lock_irq(->tree_lock);
SetPageLocked(page);
> ...
> write_unlock_irq(->tree_lock);
>
> remove_mapping:
>
> SetPageNoNewRefs();
>
> ClearPageNoNewRefs();
> write_lock_irq(->tree_lock);
>
> check page_count()
>
> page_cache_get_speculative:
>
> increment page_count()
>
> no PG_nonewrefs => return
>
> Oleg.
Shaggy
--
David Kleikamp
IBM Linux Technology Center
--
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-01 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 19:32 Oleg Nesterov
2006-08-01 15:55 ` Dave Kleikamp [this message]
2006-08-01 20:42 ` Oleg Nesterov
2006-08-01 23:53 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 6:39 Nick Piggin
2006-07-31 15:35 ` Andy Whitcroft
2006-08-01 8:45 ` Nick Piggin
2006-08-07 10:11 ` Hugh Dickins
[not found] ` <20060807132633.GD4433@wotan.suse.de>
2006-08-07 14:37 ` Hugh Dickins
2006-08-07 14:51 ` 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=1154447729.10401.16.camel@kleikamp.austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=oleg@tv-sign.ru \
/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