Re: [PATCH v5 12/18] x86/sgx: Add EPC OOM path to forcefully reclaim EPC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 18 Oct 2023 10:52:23 -0500, Michal Koutný <mkoutny@xxxxxxxx> wrote:

On Wed, Oct 18, 2023 at 08:37:25AM -0700, Dave Hansen <dave.hansen@xxxxxxxxx> wrote:
1. Admin sets a limit
2. Enclave is created
3. Enclave hits limit, allocation fails

I was actually about to suggest reorganizing the series to a part
implementing this simple limiting and a subsequent part with the reclaim
stuff for easier digestability.

Nothing else matters.

If the latter part is an unncessary overkill, it's even better.


Ok. I'll take out max_write() callback and only implement non-preemptive misc.max for EPC. I can also separate OOEPC_killing enclaves out, which is not needed if we only block allocation at limit, no need killing one enclave to make space for another. This will simplify a lot.

Thanks to all for your input!

Haitao





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux