From: Andrew Morton <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected],
xu xin <[email protected]>, Yang Yang <[email protected]>,
Ran Xiaokai <[email protected]>,
wangyong <[email protected]>,
Yunkai Zhang <[email protected]>
Subject: Re: [PATCH v3] mm/ksm: introduce ksm_force for each process
Date: Sat, 7 May 2022 10:59:26 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sat, 7 May 2022 05:47:02 +0000 [email protected] wrote:
> To use KSM, we must explicitly call madvise() in application code,
> which means installed apps on OS needs to be uninstall and source
> code needs to be modified. It is inconvenient.
>
> In order to change this situation, We add a new proc 'ksm_force'
> under /proc/<pid>/ to support turning on/off KSM scanning of a
> process's mm dynamically.
>
> If ksm_force is set as 1, force all anonymous and 'qualified' vma
> of this mm to be involved in KSM scanning without explicitly
> calling madvise to make vma MADV_MERGEABLE. But It is effctive only
> when the klob of '/sys/kernel/mm/ksm/run' is set as 1.
>
> If ksm_enale is set as 0, cancel the feature of ksm_force of this
> process and unmerge those merged pages which is not madvised as
> MERGEABLE of this process, but leave MERGEABLE areas merged.
>
There are quite a lot of typos here. Please proof-read it.
> fs/proc/base.c | 99 ++++++++++++++++++++++++++++++++++++++++
> include/linux/mm_types.h | 9 ++++
> mm/ksm.c | 32 ++++++++++++-
And please update the appropriate places under Documentation/ - all
user-facing interfaces should be well documented.
next prev parent reply other threads:[~2022-05-07 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 5:47 [PATCH v3] mm/ksm: introduce ksm_force for each process cgel.zte
2022-05-07 17:59 ` Andrew Morton [this message]
2022-05-08 9:14 ` [PATCH v4] " cgel.zte
2022-05-08 9:27 ` [PATCH v5] " cgel.zte
2022-05-08 18:03 ` Matthew Wilcox
2022-05-09 6:57 ` CGEL
2022-05-09 15:40 ` Matthew Wilcox
2022-05-10 2:23 ` CGEL
2022-05-10 20:10 ` Ammar Faizi
2022-05-10 20:30 ` Andrew Morton
2022-05-11 7:58 ` Ammar Faizi
2022-05-12 7:03 ` [PATCH v7] " cgel.zte
2022-05-12 20:41 ` Andrew Morton
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=20220507105926.d4423601230f698b0f5228d1@linux-foundation.org \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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