From: Yang Yang <yang.yang29@zte.com.cn>
To: akpm@linux-foundation.org, david@redhat.com
Cc: yang.yang29@zte.com.cn, imbrenda@linux.ibm.com,
jiang.xuexin@zte.com.cn, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com,
xu.xin16@zte.com.cn
Subject: [PATCH v8 4/6] ksm: add documentation for ksm zero pages
Date: Mon, 22 May 2023 18:53:35 +0800 [thread overview]
Message-ID: <20230522105335.4176-1-yang.yang29@zte.com.cn> (raw)
In-Reply-To: <202305221842587200002@zte.com.cn>
From: xu xin <xu.xin16@zte.com.cn>
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@zte.com.cn>
Cc: Xiaokai Ran <ran.xiaokai@zte.com.cn>
Cc: Yang Yang <yang.yang29@zte.com.cn>
Cc: Jiang Xuexin <jiang.xuexin@zte.com.cn>
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>
---
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.
+
+When ``use_zero_pages`` is/was enabled, the sum of ``pages_sharing`` +
+``ksm_zero_pages`` represents the actual number of pages saved by KSM.
+if ``use_zero_pages`` has never been enabled, ``ksm_zero_pages`` is 0.
A high ratio of ``pages_sharing`` to ``pages_shared`` indicates good
sharing, but a high ratio of ``pages_unshared`` to ``pages_sharing``
--
2.15.2
next prev parent reply other threads:[~2023-05-22 11:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 10:42 [PATCH v8 0/6] ksm: support tracking KSM-placed zero-pages yang.yang29
2023-05-22 10:49 ` [PATCH v8 1/6] ksm: support unsharing KSM-placed zero pages Yang Yang
2023-05-23 9:41 ` David Hildenbrand
2023-05-23 13:55 ` xu xin
2023-05-23 13:57 ` xu xin
2023-05-23 14:00 ` David Hildenbrand
2023-05-23 14:11 ` xu xin
2023-05-22 10:52 ` [PATCH v8 2/6] ksm: count all zero pages placed by KSM Yang Yang
2023-05-23 9:47 ` David Hildenbrand
2023-05-23 9:51 ` David Hildenbrand
2023-05-22 10:53 ` [PATCH v8 3/6] ksm: add ksm zero pages for each process Yang Yang
2023-05-23 9:55 ` David Hildenbrand
2023-05-22 10:53 ` Yang Yang [this message]
2023-05-23 9:58 ` [PATCH v8 4/6] ksm: add documentation for ksm zero pages David Hildenbrand
2023-05-22 10:54 ` [PATCH v8 5/6] ksm: update the calculation of KSM profit Yang Yang
2023-05-23 10:01 ` David Hildenbrand
2023-05-22 10:54 ` [PATCH v8 6/6] selftest: add a testcase of ksm zero pages Yang Yang
2023-05-23 10:15 ` David Hildenbrand
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=20230522105335.4176-1-yang.yang29@zte.com.cn \
--to=yang.yang29@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=xu.xin.sc@gmail.com \
--cc=xu.xin16@zte.com.cn \
/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
all inboxes | Powered by JetHome®