The patch titled
Subject: thp-vmstats-count-deferred-split-events-v2
has been removed from the -mm tree. Its filename was
thp-vmstats-count-deferred-split-events-v2.patch
This patch was dropped because it was folded into thp-vmstats-count-deferred-split-events.patch
------------------------------------------------------
From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
Subject: thp-vmstats-count-deferred-split-events-v2
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/vm/transhuge.txt | 5 +++++
1 file changed, 5 insertions(+)
diff -puN Documentation/vm/transhuge.txt~thp-vmstats-count-deferred-split-events-v2 Documentation/vm/transhuge.txt
--- a/Documentation/vm/transhuge.txt~thp-vmstats-count-deferred-split-events-v2
+++ a/Documentation/vm/transhuge.txt
@@ -229,6 +229,11 @@ thp_split_page is incremented every time
thp_split_page_failed is is incremented if kernel fails to split huge
page. This can happen if the page was pinned by somebody.
+thp_deferred_split_page is incremented when a huge page is put onto split
+ queue. This happens when a huge page is partially unmapped and
+ splitting it would free up some memory. Pages on split queue are
+ going to be split under memory pressure.
+
thp_split_pmd is incremented every time a PMD split into table of PTEs.
This can happen, for instance, when application calls mprotect() or
munmap() on part of huge page. It doesn't split huge page, only
_
Patches currently in -mm which might be from kirill@xxxxxxxxxxxxx are
thp-vmstats-count-deferred-split-events.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
