[lkml]   [2019]   [Dec]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] mm: vmscan: memcg: Add global shrink priority

> 在 2019年12月18日,22:09,Chris Down <> 写道:
> Hi Hui,
> In general cgroup v1 is in maintenance mode -- that is, excepting specific bugfixes, we don't plan to add new features.

Hi Chris,

Thanks for your review.

I will move to v2.

> Hui Zhu writes:
>> Currently, memcg has some config to limit memory usage and config
>> the shrink behavior.
>> In the memory-constrained environment, put different priority tasks
>> into different cgroups with different memory limits to protect the
>> performance of the high priority tasks. Because the global memory
>> shrink will affect the performance of all tasks. The memory limit
>> cgroup can make shrink happen inside the cgroup. Then it can decrease
>> the memory shrink of the high priority task to protect its performance.
>> But the memory footprint of the task is not static. It will change as
>> the working pressure changes. And the version changes will affect it too.
>> Then set the appropriate memory limit to decrease the global memory shrink
>> is a difficult job and lead to wasted memory or performance loss sometimes.
>> This commit adds global shrink priority to memcg to try to handle this
>> problem.
> I have significant concerns with exposing scan priority to userspace. This is an incredibly difficult metric for users to reason about since it's a reclaim implementation feature and would add to an already confusing and fragmented API in v1.
> Have you considered using memory protection (memory.low, memory.min) for this instead? It sounds like it can achieve the results you want, in that it allows you to direct and prioritise reclaim in a way that allows for ballparking (ie. it is compatible with applications with variable memory footprints).

Memory.min, low, high can affect the global shrink behavior. They can help task keep some pages to help protect performance.

But what I want is the low priority tasks (the tasks that performance is not very important) do more shrink first. And when low priority tasks doesn’t have enough pages to be dropped and system need more free page, shrink the high priority task’s pages. Because at this time, system’s stable is more important than the performance of priority task.
With memory.min and memory.low, I have no idea to config them to support this. That is why I add global shrink priority.


> Thanks,
> Chris

 \ /
  Last update: 2019-12-19 10:01    [W:0.062 / U:15.840 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site