From: Rik van Riel <riel@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Mel Gorman <mel@csn.ul.ie>,
Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: question on NUMA page migration
Date: Fri, 19 Oct 2012 11:53:30 -0400 [thread overview]
Message-ID: <5081777A.8050104@redhat.com> (raw)
Hi Andrea, Peter,
I have a question on page refcounting in your NUMA
page migration code.
In Peter's case, I wonder why you introduce a new
MIGRATE_FAULT migration mode. If the normal page
migration / compaction logic can do without taking
an extra reference count, why does your code need it?
In Andrea's case, we have a comment suggesting an
extra refcount is needed, immediately followed by
a put_page:
/*
* Pin the head subpage at least until the first
* __isolate_lru_page succeeds (__isolate_lru_page pins it
* again when it succeeds). If we unpin before
* __isolate_lru_page successd, the page could be freed and
* reallocated out from under us. Thus our previous checks on
* the page, and the split_huge_page, would be worthless.
*
* We really only need to do this if "ret > 0" but it doesn't
* hurt to do it unconditionally as nobody can reference
* "page" anymore after this and so we can avoid an "if (ret >
* 0)" branch here.
*/
put_page(page);
This also confuses me.
If we do not need the extra refcount (and I do not
understand why NUMA migrate-on-fault needs one more
refcount than normal page migration), we can get
rid of the MIGRATE_FAULT mode.
If we do need the extra refcount, why is normal
page migration safe? :)
--
All rights reversed
next reply other threads:[~2012-10-19 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 15:53 Rik van Riel [this message]
2012-10-19 16:39 ` question on NUMA page migration Peter Zijlstra
2012-10-19 17:13 ` Rik van Riel
2012-10-19 17:53 ` Peter Zijlstra
2012-10-19 18:33 ` Rik van Riel
2012-10-20 1:23 ` Ingo Molnar
2012-10-20 16:02 ` Rik van Riel
2012-10-21 12:30 ` Ingo Molnar
2012-10-21 2:39 ` Ni zhan Chen
2012-10-21 2:40 ` Rik van Riel
2012-10-21 12:31 ` Ingo Molnar
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=5081777A.8050104@redhat.com \
--to=riel@redhat.com \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).