From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Jann Horn <jannh@google.com>
Cc: Oleksandr Natalenko <oleksandr@natalenko.name>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Timofey Titovets <timofey.titovets@synesis.ru>,
Matthew Wilcox <willy@infradead.org>,
daniel@gruss.cc
Subject: Re: [PATCH V3] KSM: allow dedup all tasks memory
Date: Tue, 13 Nov 2018 14:35:21 -0800 [thread overview]
Message-ID: <CA+CK2bDPeEsFwGAQf7f=YQ+s6aUTm-ApgFd2RR5JQQr-pi-aqg@mail.gmail.com> (raw)
In-Reply-To: <CAG48ez29kArZTU=MgsVxWbuTZZ+sCrxeQ3FkDKpmQnj_MZ5hTg@mail.gmail.com>
> Wait, what? Can you name specific ones? Nowadays, enabling KSM for
> untrusted VMs seems like a terrible idea to me, security-wise.
Of course it is not used to share data among different
customers/tenants, as far as I know it is used by Oracle Cloud to
merge the same pages in clear containers.
https://medium.com/cri-o/intel-clear-containers-and-cri-o-70824fb51811
One performance enhancing feature is the use of KSM, a recent KVM
optimized for memory sharing and boot speed. Another is the use of an
optimized Clear Containers mini-OS.
Pasha
next prev parent reply other threads:[~2018-11-13 22:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<CAG48ez0ZprqUYGZFxcrY6U3Dnwt77q1NJXzzpsn1XNkRuXVppw@mail.gmail.com>
2018-11-13 14:23 ` [PATCH V3] KSM: allow dedup all tasks memory Oleksandr Natalenko
2018-11-13 17:59 ` Pavel Tatashin
2018-11-13 18:17 ` Timofey Titovets
2018-11-13 18:35 ` Pavel Tatashin
2018-11-13 18:54 ` Timofey Titovets
2018-11-13 19:16 ` Pavel Tatashin
2018-11-13 22:40 ` Timofey Titovets
2018-11-13 22:53 ` Pavel Tatashin
2018-11-13 23:07 ` Timofey Titovets
2018-11-13 20:26 ` Jann Horn
2018-11-13 22:35 ` Pavel Tatashin [this message]
2018-11-13 18:20 Timofey Titovets
[not found] <<20181112231344.7161-1-timofey.titovets@synesis.ru>
2018-11-13 11:06 ` Oleksandr Natalenko
2018-11-13 11:56 ` Timofey Titovets
2018-11-13 16:33 ` Oleksandr Natalenko
2018-11-13 17:10 ` Timofey Titovets
2018-11-13 17:27 ` Oleksandr Natalenko
2018-11-13 17:44 ` Timofey Titovets
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 23:13 Timofey Titovets
2018-11-13 1:49 ` Matthew Wilcox
2018-11-13 11:25 ` Timofey Titovets
2018-11-13 2:25 ` Pavel Tatashin
2018-11-13 11:40 ` Timofey Titovets
2018-11-13 18:42 ` Pavel Tatashin
2018-11-13 22:55 ` Timofey Titovets
2018-11-13 11:57 ` Jann Horn
2018-11-13 12:58 ` Timofey Titovets
2018-11-13 13:25 ` Jann Horn
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='CA+CK2bDPeEsFwGAQf7f=YQ+s6aUTm-ApgFd2RR5JQQr-pi-aqg@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=daniel@gruss.cc \
--cc=jannh@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksandr@natalenko.name \
--cc=timofey.titovets@synesis.ru \
--cc=willy@infradead.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).