On Thu 09-11-23 11:34:01, Gregory Price wrote: [...] > Anyway, summarizing: After a bit of reading, this does seem to map > better to the "accounting consumption" subsystem than the "constrain" > subsystem. However, if you think it's better suited for cpuset, I'm > happy to push in that direction. Maybe others see it differently but I stick with my previous position. Memcg is not a great fit for reasons already mentioned - most notably that the controller doesn't control the allocation but accounting what has been already allocated. Cpusets on the other hand constrains the allocations and that is exactly what you want to achieve. -- Michal Hocko SUSE Labs
