On Thu 08-04-21 13:29:08, Shakeel Butt wrote: > On Thu, Apr 8, 2021 at 11:01 AM Yang Shi <shy828301@xxxxxxxxx> wrote: [...] > > The low priority jobs should be able to be restricted by cpuset, for > > example, just keep them on second tier memory nodes. Then all the > > above problems are gone. Yes, if the aim is to isolate some users from certain numa node then cpuset is a good fit but as Shakeel says this is very likely not what this work is aiming for. > Yes that's an extreme way to overcome the issue but we can do less > extreme by just (hard) limiting the top tier usage of low priority > jobs. Per numa node high/hard limit would help with a more fine grained control. The configuration would be tricky though. All low priority memcgs would have to be carefully configured to leave enough for your important processes. That includes also memory which is not accounted to any memcg. The behavior of those limits would be quite tricky for OOM situations as well due to a lack of NUMA aware oom killer. -- Michal Hocko SUSE Labs
