From: Jianyu Zhan <nasa4836@gmail.com>
To: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
riel@redhat.com, liuj97@gmail.com, peterz@infradead.org,
hannes@cmpxchg.org, mgorman@suse.de, aarcange@redhat.com,
sasha.levin@oracle.com, liwanp@linux.vnet.ibm.com,
nasa4836@gmail.com, khalid.aziz@oracle.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC 2/2] mm: introdule compound_head_by_tail()
Date: Sun, 27 Apr 2014 21:36:24 +0800 [thread overview]
Message-ID: <2c87e00d633153ba7b710bab12710cc3a58704dd.1398605516.git.nasa4836@gmail.com> (raw)
In-Reply-To: <c232030f96bdc60aef967b0d350208e74dc7f57d.1398605516.git.nasa4836@gmail.com>
In put_comound_page(), we call compound_head() after !PageTail
check fails, so in compound_head() PageTail is quite likely to
be true, but instead it is checked with:
if (unlikely(PageTail(page)))
in this case, this unlikely macro is a negative hint for compiler.
So this patch introduce compound_head_by_tail() which deal with
a possible tail page(though it could be spilt by a racy thread),
and make compound_head() a wrapper on it.
Signed-off-by: Jianyu Zhan <nasa4836@gmail.com>
---
include/linux/mm.h | 34 ++++++++++++++++++++++------------
mm/swap.c | 2 +-
2 files changed, 23 insertions(+), 13 deletions(-)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index bf9811e..1bc7baf 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -405,20 +405,30 @@ static inline void compound_unlock_irqrestore(struct page *page,
#endif
}
+/**
+ * Note: this function must be called on a possible tail page,
+ * this tail page may not be tail anymore upon we calling this funciton,
+ * because we may race with __split_huge_page_refcount tearing down it.
+ */
+static inline struct page *compound_head_by_tail(struct page *page)
+{
+ struct page *head = page->first_page;
+
+ /*
+ * page->first_page may be a dangling pointer to an old
+ * compound page, so recheck that it is still a tail
+ * page before returning.
+ */
+ smp_rmb();
+ if (likely(PageTail(page)))
+ return head;
+ return page;
+}
+
static inline struct page *compound_head(struct page *page)
{
- if (unlikely(PageTail(page))) {
- struct page *head = page->first_page;
-
- /*
- * page->first_page may be a dangling pointer to an old
- * compound page, so recheck that it is still a tail
- * page before returning.
- */
- smp_rmb();
- if (likely(PageTail(page)))
- return head;
- }
+ if (unlikely(PageTail(page)))
+ return compound_head_by_tail(page);
return page;
}
diff --git a/mm/swap.c b/mm/swap.c
index 0d8d891..0b05355 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -256,7 +256,7 @@ static void put_compound_page(struct page *page)
* Case 3 is possible, as we may race with
* __split_huge_page_refcount tearing down a THP page.
*/
- head_page = compound_head(page);
+ head_page = compound_head_by_tail(page);
if (!__compound_tail_refcounted(head_page))
put_unrefcounted_compound_page(head_page, page);
else
--
2.0.0-rc1
--
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:[~2014-04-27 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 13:35 [PATCH RFC 1/2] mm/swap.c: split put_compound_page function Jianyu Zhan
2014-04-27 13:36 ` Jianyu Zhan [this message]
2014-04-28 14:54 ` [PATCH RFC 2/2] mm: introdule compound_head_by_tail() Michal Hocko
2014-04-28 15:53 ` Jianyu Zhan
2014-04-28 15:55 ` Peter Zijlstra
2014-04-28 16:23 ` Jianyu Zhan
2014-04-28 18:23 ` Michal Hocko
2014-04-28 15:00 ` [PATCH RFC 1/2] mm/swap.c: split put_compound_page function Michal Hocko
2014-04-28 15:54 ` Jianyu Zhan
2014-04-28 16:43 ` Khalid Aziz
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=2c87e00d633153ba7b710bab12710cc3a58704dd.1398605516.git.nasa4836@gmail.com \
--to=nasa4836@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=khalid.aziz@oracle.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=sasha.levin@oracle.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