From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-mm@kvack.org
Cc: nefelim4ag@gmail.com, marco.antonio.780@gmail.com,
linux-kernel@vger.kernel.org, tonyb@cybernetics.com,
killertofu@gmail.com
Subject: [PATCH V3 3/4] KSM: Add config to control mark_new_vma
Date: Tue, 11 Nov 2014 15:57:35 +0300 [thread overview]
Message-ID: <1415710656-29296-4-git-send-email-nefelim4ag@gmail.com> (raw)
In-Reply-To: <1415710656-29296-1-git-send-email-nefelim4ag@gmail.com>
Allowing to control mark_new_vma default value
Allowing work ksm on early allocated vmas
Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
---
mm/Kconfig | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/mm/Kconfig b/mm/Kconfig
index 1d1ae6b..90f40a6 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -340,6 +340,13 @@ config KSM
until a program has madvised that an area is MADV_MERGEABLE, and
root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set).
+config KSM_MARK_NEW_VMA
+ int "Marking new vma pages as VM_MERGEABLE"
+ depends on KSM
+ default 0
+ range 0 1
+ help
+
config DEFAULT_MMAP_MIN_ADDR
int "Low address space to protect from user allocation"
depends on MMU
--
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-11 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 12:57 [PATCH V3 0/4] KSM: Mark new vma for deduplication Timofey Titovets
2014-11-11 12:57 ` [PATCH V3 1/4] KSM: Add auto flag new VMA as VM_MERGEABLE Timofey Titovets
2014-11-11 12:57 ` [PATCH V3 2/4] KSM: Add to sysfs - mark_new_vma Timofey Titovets
2014-11-11 12:57 ` Timofey Titovets [this message]
2014-11-11 12:57 ` [PATCH V3 4/4] KSM: mark_new_vma added to Documentation 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=1415710656-29296-4-git-send-email-nefelim4ag@gmail.com \
--to=nefelim4ag@gmail.com \
--cc=killertofu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marco.antonio.780@gmail.com \
--cc=tonyb@cybernetics.com \
/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