From: <xu.xin16@zte.com.cn>
To: <akpm@linux-foundation.org>, <david@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<shr@devkernel.io>
Subject: [PATCH linux-next v2] ksm: add ksm involvement information for each process
Date: Fri, 26 Apr 2024 09:46:19 +0800 (CST) [thread overview]
Message-ID: <20240426094619962AxIC6CSpfpJNeiy8HRA9h@zte.com.cn> (raw)
From: xu xin <xu.xin16@zte.com.cn>
In /proc/<pid>/ksm_stat, Add two extra ksm involvement items including
MMF_VM_MERGEABLE and MMF_VM_MERGE_ANY. It helps administrators to
better know the system's KSM behavior at process level.
KSM_mergeable: yes/no
whether the process'mm is added by madvise() into the candidate list
of KSM or not.
KSM_merge_any: yes/no
whether the process'mm is added by prctl() into the candidate list
of KSM or not, and fully enabled at process level.
Changelog
=========
v1 -> v2:
replace the internal flag names with straightforward strings.
* MMF_VM_MERGEABLE -> KSM_mergeable
* MMF_VM_MERGE_ANY -> KSM_merge_any
Signed-off-by: xu xin <xu.xin16@zte.com.cn>
---
fs/proc/base.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 18550c071d71..50e808ffcda4 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -3217,6 +3217,10 @@ static int proc_pid_ksm_stat(struct seq_file *m, struct pid_namespace *ns,
seq_printf(m, "ksm_zero_pages %lu\n", mm->ksm_zero_pages);
seq_printf(m, "ksm_merging_pages %lu\n", mm->ksm_merging_pages);
seq_printf(m, "ksm_process_profit %ld\n", ksm_process_profit(mm));
+ seq_printf(m, "KSM_mergeable: %s\n",
+ test_bit(MMF_VM_MERGEABLE, &mm->flags) ? "yes" : "no");
+ seq_printf(m, "KSM_merge_any: %s\n",
+ test_bit(MMF_VM_MERGE_ANY, &mm->flags) ? "yes" : "no");
mmput(mm);
}
--
2.15.2
next reply other threads:[~2024-04-26 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 1:46 xu.xin16 [this message]
2024-04-26 8:13 ` David Hildenbrand
2024-05-11 8:12 ` xu xin
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=20240426094619962AxIC6CSpfpJNeiy8HRA9h@zte.com.cn \
--to=xu.xin16@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shr@devkernel.io \
/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®