From: cgel.zte@gmail.com
To: akpm@linux-foundation.org
Cc: hughd@google.com, izik.eidus@ravellosystems.com,
willy@infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, xu xin <xu.xin16@zte.com.cn>
Subject: [RFC PATCH 0/4] propose a auto-run mode for ksm
Date: Wed, 3 Aug 2022 10:03:06 +0000 [thread overview]
Message-ID: <20220803100306.1653382-1-xu.xin16@zte.con.cn> (raw)
From: xu xin <xu.xin16@zte.com.cn>
The following patch series bring a NEW running state "auto mode". In
traditional KSM, whether ksmd works scanning and merging or not
depends on the sysfs klob ksm_run.
Most of time, letting ksmd run is not very much needed, for example,
when memory is sufficient, because it increases the delays of COW for
user applications and also consume some cpu resource.
Besides, the fixed pages_to_scan is not always good. When there are a
lot of same pages, the default pages_to_scan makes ksmd so slow to merge
them.
The four patches try to optimize the above two points with a auto mode.
It's a lightweight optimization to KSM.
xu xin (4):
ksm: propose a auto-run mode of ksm
ksm: implement scan-enhanced algorithm of auto mode
ksm: let ksmd work automatically with memory threshold
ksm: show ksmd status of auto mode
mm/ksm.c | 212 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 206 insertions(+), 6 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-03 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 10:03 cgel.zte [this message]
2022-08-03 10:05 ` [RFC PATCH 1/4] ksm: propose a auto-run mode of ksm cgel.zte
2022-08-03 10:05 ` [RFC PATCH 2/4] ksm: implement scan-enhanced algorithm of auto mode cgel.zte
2022-08-03 10:05 ` [RFC PATCH 3/4] ksm: let ksmd work automatically with memory threshold cgel.zte
2022-08-03 10:05 ` [RFC PATCH 4/4] ksm: show ksmd status of auto mode cgel.zte
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=20220803100306.1653382-1-xu.xin16@zte.con.cn \
--to=cgel.zte@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=izik.eidus@ravellosystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).