From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stefan Roesch <shr@devkernel.io>, kernel-team@fb.com
Cc: linux-mm@kvack.org, riel@surriel.com, mhocko@suse.com,
david@redhat.com, linux-doc@vger.kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org
Subject: Re: [PATCH v1] docs/mm: extend ksm doc
Date: Wed, 15 Mar 2023 10:59:53 +0700 [thread overview]
Message-ID: <ZBFCud+I8mVAoh87@debian.me> (raw)
In-Reply-To: <20230314204557.3863923-1-shr@devkernel.io>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Tue, Mar 14, 2023 at 01:45:57PM -0700, Stefan Roesch wrote:
> +to cancel that advice and restore unshared pages: whereupon KSM
> +unmerges whatever is merged for that process. Note: this unmerging call
> +may suddenly require more memory than is available - possibly failing
> +with EAGAIN, but more probably arousing the Out-Of-Memory killer.
"... to disable KSM and let it unmerges ... . Note that this unmerging
call may exhaust memory and triggers OOM killer."
> +However, if the system is dedicated to running multiple jobs within the
> +same security domain, there is a usecase where multiple instances of the
> +same job are running inside a safe shared security domain and using the
> +same sensitive data.
"... it is possible for multiple instances ... and share the same
sensitive data."
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-15 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 20:45 Stefan Roesch
2023-03-15 3:59 ` Bagas Sanjaya [this message]
2023-03-15 4:28 ` Randy Dunlap
2023-03-15 15:59 ` Stefan Roesch
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=ZBFCud+I8mVAoh87@debian.me \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--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