TCSNum vs TCSMaxNum

Intel® Software Guard Extensions (Intel® SGX)

Discussion board focused on hardware-based isolation and memory encryption to provide extended code protection in solutions.

TCSNum vs TCSMaxNum

391 Views

Hello,

<EnclaveConfiguration>
  <ProdID>0</ProdID>
  <ISVSVN>0</ISVSVN>
  <StackMaxSize>0x40000</StackMaxSize>
  <HeapMaxSize>0x1000000</HeapMaxSize>
  <TCSNum>75</TCSNum>
  <TCSMaxNum>150</TCSMaxNum>
  <TCSMinPool>25</TCSMinPool>
  <TCSPolicy>1</TCSPolicy>
  <DisableDebug>1</DisableDebug>
  <MiscSelect>0</MiscSelect>
  <MiscMask>0xFFFFFFFF</MiscMask>
</EnclaveConfiguration>

In the above enclave configuration file, I have several queries regarding TCS.
Given the TCSNum and TCSMaxNum, how many threads will be spawned initially, and how does it scale? If it does scale, what criteria determine its scaling?

Additionally, apart from the binding policy, I'm uncertain if the No. of TCS correlates with switchless worker threads .

Kindly assist me. Thank you in advance

Link Copied

0 Replies

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.