archive mirror
 help / color / mirror / Atom feed
* Re: SGX Information needed
       [not found] ` <>
@ 2022-09-27  8:27   ` Huang, Kai
  0 siblings, 0 replies; only message in thread
From: Huang, Kai @ 2022-09-27  8:27 UTC (permalink / raw)
  To: linux-sgx, Hansen, Dave, Patel, Himanshu
  Cc: Kuvaiskii, Dmitrii, Hossain, Md Iqbal

On Tue, 2022-09-27 at 07:41 +0000, Patel, Himanshu wrote:
> Please explain me the process for my below questions. 
> Thanks
> Himanshu
> From: Patel, Himanshu 
> Sent: Tuesday, September 27, 2022 10:48 AM
> To: Hansen, Dave <>; Huang, Kai <>
> Cc: Hossain, Md Iqbal <>; Kuvaiskii, Dmitrii
> <>
> Subject: SGX Information needed
> Hi Dave/Kai,
> I have some questions related to SGX. I am putting a scenario here.
> suppose we have 16G PRM (per socket) and sgx_enclave_size=64G , so workload
> will need remote socket's enclave memory as well right.
> which entity (SGX driver?) is doing the job to decide remote sockets to
> fulfill workload's requirement?
> If SGX driver is deciding , it must be looking somewhere(like any mapped table
> or anything else) to select remote sockets, what it that?

Hi Himanshu,

Jarkko should be the person to answer, but I'll try first:  

Yes the SGX driver decides which node(s) to allocate.  Firstly the drive tries
to allocate from the local node.  If local node is running out of EPC page, the
driver tries to allocate EPC page from the 'next-highest node' (i.e. node 0 -> 1
-> 2 ...).

EPC doesn't have its own SRAT type, so it depends on SRAT table's memory
resource (which covers EPC in  practice, if I recall correctly)  affinity to
decide which EPC page belongs to which node.

Hope above helps.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-09-27  8:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <>
     [not found] ` <>
2022-09-27  8:27   ` SGX Information needed Huang, Kai

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