From: xu.xin.sc@gmail.com
To: akpm@linux-foundation.org, david@redhat.com, imbrenda@linux.vnet.ibm.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
xu xin <xu.xin16@zte.com.cn>
Subject: [PATCH 0/3] ksm: fix incorrect count of merged pages when enabling use_zero_pages
Date: Thu, 29 Sep 2022 02:52:06 +0000 [thread overview]
Message-ID: <20220929025206.280970-1-xu.xin16@zte.com.cn> (raw)
From: xu xin <xu.xin16@zte.com.cn>
Before enabling use_zero_pages by setting /sys/kernel/mm/ksm/
use_zero_pages to 1, pages_sharing of KSM is basically accurate. But
after enabling use_zero_pages, all empty pages that are merged with
kernel zero page are not counted in pages_sharing or pages_shared.
That is because the rmap_items of these ksm zero pages are not
appended to The Stable Tree of KSM.
We need to add the count of empty pages to let users know how many empty
pages are merged with kernel zero page(s).
Please see the subsequent patches for details.
*** BLURB HERE ***
xu xin (3):
ksm: abstract the function try_to_get_old_rmap_item
ksm: add the accounting of zero pages merged by use_zero_pages
ksm: add zero_pages_merged in Documentation
Documentation/admin-guide/mm/ksm.rst | 10 ++-
mm/ksm.c | 122 +++++++++++++++++++++------
2 files changed, 106 insertions(+), 26 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-29 2:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 2:52 xu.xin.sc [this message]
2022-09-29 2:59 ` [PATCH 1/3] ksm: abstract the function try_to_get_old_rmap_item xu.xin.sc
2022-09-29 3:00 ` [PATCH 2/3] ksm: add the accounting of zero pages merged by use_zero_pages xu.xin.sc
2022-09-29 3:00 ` [PATCH 3/3] ksm: add zero_pages_sharing in Documentation xu.xin.sc
2022-09-29 9:21 ` [PATCH 0/3] ksm: fix incorrect count of merged pages when enabling use_zero_pages David Hildenbrand
2022-09-29 10:36 ` Claudio Imbrenda
2022-09-29 11:12 ` David Hildenbrand
2022-09-29 12:05 ` Claudio Imbrenda
2022-09-29 17:53 ` David Hildenbrand
2022-09-30 9:30 ` Claudio Imbrenda
2022-09-30 9:40 ` David Hildenbrand
2022-09-29 11:13 ` Reply:[PATCH " xu xin
2022-09-29 10:42 ` [PATCH " Claudio Imbrenda
2022-09-29 11:34 ` David Hildenbrand
2022-09-29 11:51 ` Claudio Imbrenda
2022-09-30 2:00 ` Reply:[PATCH " xu xin
2022-09-30 9:41 ` Claudio Imbrenda
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=20220929025206.280970-1-xu.xin16@zte.com.cn \
--to=xu.xin.sc@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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