All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: 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: Tue, 2 Feb 2021 19:44:42 +0200	[thread overview]
Message-ID: <YBmPiqfHLz5JV57y@kernel.org> (raw)
In-Reply-To: <cb04f65c-7598-e5c0-6aa9-421b8e37c8db@gmail.com>

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.

> > 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.

/Jarkko

  reply	other threads:[~2021-02-02 17:48 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 [this message]
2021-02-03  8:11         ` Michael Kerrisk (man-pages)

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=YBmPiqfHLz5JV57y@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mtk.manpages@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.