From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Dave Kleikamp <shaggy@austin.ibm.com>,
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: Wed, 02 Aug 2006 09:53:49 +1000 [thread overview]
Message-ID: <44CFE98D.2060901@yahoo.com.au> (raw)
In-Reply-To: <20060801204202.GA223@oleg>
Oleg Nesterov wrote:
> On 08/01, Dave Kleikamp wrote:
>>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.
>
>
> No, I think it is I who missed something, thanks.
Yeah, SetPageNoNewRefs is indeed called only under PageLocked or for
newly allocated pages. I should make a note about that, as it isn't
immediately clear.
Thanks
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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 23:53 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
2006-08-01 20:42 ` Oleg Nesterov
2006-08-01 23:53 ` Nick Piggin [this message]
-- 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=44CFE98D.2060901@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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 \
--cc=shaggy@austin.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