> A module param which the admin used to adjust the overcommit percentage was proposed to handle cases like this where users would want to determine the level of overcommit they allowed. Would something like this be used by your users? A module param with a high default value (in GBs for CFL systems) would allow flexibility. Would changing the module param require a reboot or just a module reload? ________________________________________ From: Accardi, Kristen C <kristen.c.accardi@xxxxxxxxx> Sent: Monday, January 31, 2022 9:40 AM To: linux-sgx@xxxxxxxxxxxxxxx; Anand Krishnamoorthi Subject: [EXTERNAL] Re: [PATCH v3 1/2] x86/sgx: Add accounting for tracking overcommit On Fri, 2022-01-28 at 01:30 +0000, Anand Krishnamoorthi wrote: > Some of our users rely on EPC paging to run enclaves that require GBs > of memory on Coffee Lake VMs with less than 200MB EPC. > Would the 1.5x EPC backing pages limit prevent these users from > running their enclaves? > > - Anand If you had 200MB of EPC, you'd be limited to 300MB of backing pages. The goal of this patch was to prevent users from using up all the memory on the system with backing pages, which having GB of backing pages would do pretty quickly. A module param which the admin used to adjust the overcommit percentage was proposed to handle cases like this where users would want to determine the level of overcommit they allowed. Would something like this be used by your users?
