From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org, Timofey Titovets <nefelim4ag@gmail.com>
Subject: [RESEND][PATCH V3 4/4] KSM: mark_new_vma added to Documentation.
Date: Fri, 14 Nov 2014 00:01:58 +0300 [thread overview]
Message-ID: <1415912518-8508-5-git-send-email-nefelim4ag@gmail.com> (raw)
In-Reply-To: <1415912518-8508-1-git-send-email-nefelim4ag@gmail.com>
Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
---
Documentation/vm/ksm.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/vm/ksm.txt b/Documentation/vm/ksm.txt
index f34a8ee..880fdbf 100644
--- a/Documentation/vm/ksm.txt
+++ b/Documentation/vm/ksm.txt
@@ -24,6 +24,8 @@ KSM only operates on those areas of address space which an application
has advised to be likely candidates for merging, by using the madvise(2)
system call: int madvise(addr, length, MADV_MERGEABLE).
+Also KSM can mark anonymous memory as mergeable, see below.
+
The app may call int madvise(addr, length, MADV_UNMERGEABLE) to cancel
that advice and restore unshared pages: whereupon KSM unmerges whatever
it merged in that range. Note: this unmerging call may suddenly require
@@ -73,6 +75,11 @@ merge_across_nodes - specifies if pages from different numa nodes can be merged.
merge_across_nodes, to remerge according to the new setting.
Default: 1 (merging across nodes as in earlier releases)
+mark_new_vma - set 0 to disallow ksm marking every new allocated anonymous
+ memory as mergeable.
+ set 1 to allow ksm mark every new allocated anonymous memory
+ as mergeable
+
run - set 0 to stop ksmd from running but keep merged pages,
set 1 to run ksmd e.g. "echo 1 > /sys/kernel/mm/ksm/run",
set 2 to stop ksmd and unmerge all pages currently merged,
--
2.1.3
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-11-13 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 21:01 [RESEND][PATCH V3 0/4] KSM: Mark new vma for deduplication Timofey Titovets
2014-11-13 21:01 ` [RESEND][PATCH V3 1/4] KSM: Add auto flag new VMA as VM_MERGEABLE Timofey Titovets
2014-11-13 21:01 ` [RESEND][PATCH V3 2/4] KSM: Add to sysfs - mark_new_vma Timofey Titovets
2014-11-13 21:01 ` [RESEND][PATCH V3 3/4] KSM: Add config to control mark_new_vma Timofey Titovets
2014-11-13 21:01 ` Timofey Titovets [this message]
2014-12-01 10:35 ` [RESEND][PATCH V3 0/4] KSM: Mark new vma for deduplication Hugh Dickins
2014-12-07 15:20 ` Timofey Titovets
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=1415912518-8508-5-git-send-email-nefelim4ag@gmail.com \
--to=nefelim4ag@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/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).