Hi Michal,
On Thu, 04 Jan 2024 06:38:41 -0600, Michal Koutný <mkoutny@xxxxxxxx> wrote:
Hello.
On Mon, Dec 18, 2023 at 03:24:40PM -0600, Haitao Huang
<haitao.huang@xxxxxxxxxxxxxxx> wrote:
Thanks for raising this. Actually my understanding the above discussion
was
mainly about not doing reclaiming by killing enclaves, i.e., I assumed
"reclaiming" within that context only meant for that particular kind.
As Mikko pointed out, without reclaiming per-cgroup, the max limit of
each
cgroup needs to accommodate the peak usage of enclaves within that
cgroup.
That may be inconvenient for practical usage and limits could be forced
to
be set larger than necessary to run enclaves performantly. For example,
we
can observe following undesired consequences comparing a system with
current
kernel loaded with enclaves whose total peak usage is greater than the
EPC
capacity.
1) If a user wants to load the same exact enclaves but in separate
cgroups,
then the sum of cgroup limits must be higher than the capacity and the
system will end up doing the same old global reclaiming as it is
currently
doing. Cgroup is not useful at all for isolating EPC consumptions.
That is the use of limits to prevent a runaway cgroup smothering the
system. Overcommited values in such a config are fine because the more
simultaneous runaways, the less likely.
The peak consumption is on the fair expense of others (some efficiency)
and the limit contains the runaway (hence the isolation).
This makes sense to me in theory. Mikko, Chris Y/Bo Z, your thoughts on
whether this is good enough for your intended usages?
2) To isolate impact of usage of each cgroup on other cgroups and yet
still
being able to load each enclave, the user basically has to carefully
plan to
ensure the sum of cgroup max limits, i.e., the sum of peak usage of
enclaves, is not reaching over the capacity. That means no
over-commiting
allowed and the same system may not be able to load as many enclaves as
with
current kernel.
Another "config layout" of limits is to achieve partitioning (sum ==
capacity). That is perfect isolation but it naturally goes against
efficient utilization. The way other controllers approach this trade-off
is with weights (cpu, io) or protections (memory). I'm afraid misc
controller is not ready for this.
My opinion is to start with the simple limits (first patches) and think
of prioritization/guarantee mechanism based on real cases.
We moved away from using mem like custom controller with (low, high, max)
to misc controller. But if we need add those down the road, then the
interface needs be changed. So my concern on this route would be whether
misc would allow any of those extensions. On the other hand, it might turn
out less complex just doing the reclamation per cgroup.
Thanks a lot for your comments and they are really helpful!
Haitao
