On Thu 19-09-19 21:13:32, Hillf Danton wrote: > > Currently memory controler is playing increasingly important role in > how memory is used and how pages are reclaimed on memory pressure. > > In daily works memcg is often created for critical tasks and their pre > configured memory usage is supposed to be met even on memory pressure. > Administrator wants to make it configurable that the pages consumed by > memcg-B can be reclaimed by page allocations invoked not by memcg-A but > by memcg-C. I am not really sure I understand the usecase well but this sounds like what memory reclaim protection in v2 is aiming at. > That configurability is addressed by adding priority for soft limit > reclaiming to make sure that no pages will be reclaimed from memcg of > higer priortiy in favor of memcg of lower priority. cgroup v1 interfaces are generally frozen and mostly aimed at backward compatibility. I am especially concerned about adding a new way to control soft limit which is known to be misdesigned and unfixable to behave reasonably. > Pages are reclaimed with no priority being taken into account by default > unless user turns it on, and then they are responsible for their smart > activities almost the same way as they play realtime FIFO/RR games. > > Priority is available only in the direct reclaiming context in order to > advoid churning in the complex kswapd behavior. > > Cc: Shakeel Butt <shakeelb@xxxxxxxxxx> > Cc: Roman Gushchin <guro@xxxxxx> > Cc: Matthew Wilcox <willy@xxxxxxxxxxxxx> > Cc: Johannes Weiner <hannes@xxxxxxxxxxx> > Cc: Michal Hocko <mhocko@xxxxxxx> > Signed-off-by: Hillf Danton <hdanton@xxxxxxxx> That being said, you should describe the usecase and explain why v2 interface is not providing what you need. We might think about where to go from there but extending the soft limit reclaim is almost certainly not the right way to go. -- Michal Hocko SUSE Labs
