From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-sgx@vger.kernel.org, dave.hansen@linux.intel.com
Subject: Re: [PATCH v2] sgx.7: New page with overview of Software Guard eXtensions (SGX)
Date: Wed, 3 Feb 2021 09:11:15 +0100 [thread overview]
Message-ID: <fcd5531f-3d8b-491f-6949-9e20a47882fb@gmail.com> (raw)
In-Reply-To: <YBmPiqfHLz5JV57y@kernel.org>
Hello Jarkko,
On 2/2/21 6:44 PM, Jarkko Sakkinen wrote:
> On Thu, Jan 21, 2021 at 03:33:05PM +0100, Michael Kerrisk (man-pages) wrote:
>> Hi Jarko,
>
> Jarkko :-)
>
>> On 1/21/21 12:18 PM, Jarkko Sakkinen wrote:
>>> On Tue, Dec 22, 2020 at 07:53:24PM +0100, Michael Kerrisk (man-pages) wrote:
>>>>> * Fixed the semantic newlines convention and various style errors etc.
>>>>> that were reported by Alenjandro and Michael.
>>
>> s/Alenjandro/Alejandro/ :-)
>
> Just had to mention the typo above because of this, sorry :-) I'll
> fix this.
Got it. Not enough practivce with Finnish :-)
>>> So the thing is that there is reserved memory, consider it as a bit like
>>> VRAM. This memory can be oversubscribed. Then when you create an enclave
>>> you consume these pages. When running out of them, the kernel swaps pages
>>> from enclaves across the system currently based on a trivial FIFO policy.
>>> So these regions define kind of the memory pool for all enclaves running in
>>> the system.
>>
>> SO, is there some suitable change for the manual page text?
>
> What if I just edit it from this? I think the video RAM comparison makes
> this common sense understandable. There's restricted memory shared by
> processes and managed by the kernel.
That sounds okay to me.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-02-03 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 0:41 [PATCH v2] sgx.7: New page with overview of Software Guard eXtensions (SGX) Jarkko Sakkinen
2020-12-22 18:53 ` Michael Kerrisk (man-pages)
2021-01-21 11:18 ` Jarkko Sakkinen
2021-01-21 14:33 ` Michael Kerrisk (man-pages)
2021-02-02 17:44 ` Jarkko Sakkinen
2021-02-03 8:11 ` Michael Kerrisk (man-pages) [this message]
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=fcd5531f-3d8b-491f-6949-9e20a47882fb@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-sgx@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