linux-kernel - Re: [PATCH] mm: vmscan: memcg: Add global shrink priority

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1E6A7BC4-A983-4C65-9DA9-4D3A26D4D31D@linux.alibaba.com>
Date:   Sun, 29 Dec 2019 21:38:00 +0800
From:   teawater <teawaterz@...ux.alibaba.com>
To:     Chris Down <chris@...isdown.name>
Cc:     Johannes Weiner <hannes@...xchg.org>,
        Michal Hocko <mhocko@...nel.org>,
        Vladimir Davydov <vdavydov.dev@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Roman Gushchin <guro@...com>,
        Shakeel Butt <shakeelb@...gle.com>,
        Yang Shi <yang.shi@...ux.alibaba.com>, tj@...nel.org,
        tglx@...utronix.de, linux-kernel@...r.kernel.org,
        cgroups@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] mm: vmscan: memcg: Add global shrink priority



> 在 2019年12月19日，19:26，Chris Down <chris@...isdown.name> 写道：
> 
> Hi Hui,
> 
> teawater writes:
>> 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.
> 
> For sure, that's what I'm suggesting you use memory.{min,low} for -- you define some subset of the cgroup hierarchy as "protected", and then you bias reclaim away from protected cgroups (and thus *towards* unprotected cgroups) by biasing the size of LRU scanning. See my patch that went into 5.4 and the examples in the commit message:
> 
>    commit 9783aa9917f8ae24759e67bf882f1aba32fe4ea1
>    Author: Chris Down <chris@...isdown.name>
>    Date:   Sun Oct 6 17:58:32 2019 -0700
> 
>        mm, memcg: proportional memory.{low,min} reclaim
> 
> You can see how we're using memory.{low,min} to achieve this in this case study[0]. It's not exactly equivalent technically to your solution, but the end goals are similar.
> 
> Thanks,
> 
> Chris
> 
> 0: https://facebookmicrosites.github.io/cgroup2/docs/overview.html#case-study-the-fbtax2-project

Hi Chris,

I have another idea about global shrink priority.

In the memory-constrained and complex multitasking environment such as an Android system may require more complex performance priority.
For example, the tasks of app in the font, they need high priority because low priority will affect the user experience at once.
The tasks of app in background should have lower priority than the first one.  And sometime, each app should have different priority.  Because some apps are frequently used.  They should have high priority than other background apps.
The daemons should have lower priority than background apps.  Because most of them will not affect the user experience.

Do you think this environment is suitable for global shrink priority.

Best,
Hui