The patch titled
Subject: mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim-fix
has been added to the -mm tree. Its filename is
mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim-fix.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Shaohua Li <shli@xxxxxxxxxx>
Subject: mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim-fix
document split_huge_page_to_list
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/huge_memory.c | 7 +++++++
1 file changed, 7 insertions(+)
diff -puN mm/huge_memory.c~mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim-fix mm/huge_memory.c
--- a/mm/huge_memory.c~mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim-fix
+++ a/mm/huge_memory.c
@@ -1800,6 +1800,13 @@ static void __split_huge_page(struct pag
BUG_ON(mapcount != mapcount2);
}
+/*
+ * Split a hugepage into normal pages. This doesn't change the position of head
+ * page. If @list is null, tail pages will be added to LRU list, otherwise, to
+ * @list. Both head page and tail pages will inherit mapping, flags, and so on
+ * from the hugepage.
+ * Return 0 if the hugepage is split successfully otherwise return 1.
+ */
int split_huge_page_to_list(struct page *page, struct list_head *list)
{
struct anon_vma *anon_vma;
_
Patches currently in -mm which might be from shli@xxxxxxxxxx are
linux-next.patch
mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim.patch
mm-thp-add-split-tail-pages-to-shrink-page-list-in-page-reclaim-fix.patch
kernel-smpc-cleanups.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
