On 22.05.23 12:53, Yang Yang wrote:
From: xu xin <xu.xin16@xxxxxxxxxx>
Add the description of ksm_zero_pages.
When use_zero_pages is enabled, pages_sharing cannot represent how
much memory saved actually by KSM, but the sum of ksm_zero_pages +
pages_sharing does.
Signed-off-by: xu xin <xu.xin16@xxxxxxxxxx>
Cc: Xiaokai Ran <ran.xiaokai@xxxxxxxxxx>
Cc: Yang Yang <yang.yang29@xxxxxxxxxx>
Cc: Jiang Xuexin <jiang.xuexin@xxxxxxxxxx>
Cc: Claudio Imbrenda <imbrenda@xxxxxxxxxxxxx>
Cc: David Hildenbrand <david@xxxxxxxxxx>
---
Documentation/admin-guide/mm/ksm.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/admin-guide/mm/ksm.rst b/Documentation/admin-guide/mm/ksm.rst
index 7626392fe82c..019dc40a0d3c 100644
--- a/Documentation/admin-guide/mm/ksm.rst
+++ b/Documentation/admin-guide/mm/ksm.rst
@@ -173,6 +173,14 @@ stable_node_chains
the number of KSM pages that hit the ``max_page_sharing`` limit
stable_node_dups
number of duplicated KSM pages
+ksm_zero_pages
+ how many empty pages are sharing the kernel zero page(s) instead
+ of other user pages as it would happen normally. Only meaningful
+ when ``use_zero_pages`` is/was enabled.
"empty pages" is misleading. You can probably drop the last comment,
because you repeat that afterwards.
how many zero pages that are still mapped into processes were mapped by
KSM when deduplicating.
I suggest squashing this patch into #3.
--
Thanks,
David / dhildenb
