From: Mark <zxm927@163.com>
To: hugh.dickins@tiscali.co.uk, linux-kernel@vger.kernel.org
Subject: The security about KSM and "adds all memory pages from all processes to KSM"
Date: Wed, 28 Jun 2017 22:25:38 +0800 (CST) [thread overview]
Message-ID: <6cc450ca.e8da.15cef17e0ba.Coremail.zxm927@163.com> (raw)
Hi Hugh and experts,
We are trying to enable KSM in a multi-container projects to save some memory.
And as the celld project suggests:
"To maximize the benefit of KSM, CellD uses a custom system call which adds all
memory pages from all processes to the set of pages KSM attempts to merge. " [1]
Our test shows that with the patch[2], applications works stable and more memory
are saved, but we are not sure if this patch brings in any more secure risks compared
with ksm only. The "uksm"[3] probably works in a similar way, but somehow in our
tests seems it save less memory.
Do you have any comments? Thank you so much.
[1] http://systems.cs.columbia.edu/archive/pub/2012/08/the-design-implementation-and-evaluation-of-cells-a-virtual-smartphone-architecture/
[2] https://cells-source.cs.columbia.edu/#/c/114/1/mm/madvise.c
[3] http://kerneldedup.org/en/
reply other threads:[~2017-06-28 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6cc450ca.e8da.15cef17e0ba.Coremail.zxm927@163.com \
--to=zxm927@163.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®