linux-kernel - Re: [PATCH] mm/vmscan.c: drop_slab

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] [day] [month] [year] [list]

Message-ID: <YGycedyGoUTcvX09@dhcp22.suse.cz>
Date:   Tue, 6 Apr 2021 19:38:01 +0200
From:   Michal Hocko <mhocko@...e.com>
To:     Neil Sun <neilsun@...ify.com>
Cc:     akpm@...ux-foundation.org, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg

On Tue 06-04-21 23:12:34, Neil Sun wrote:
> 
> 
> On 2021/4/6 22:39, Michal Hocko wrote:
> > 
> > Have you considered using high limit for the pro-active memory reclaim?
> 
> Thanks, Michal, do you mean the procfs interfaces?
> We have set vm.vfs_cache_pressure=1000 and so on.
> would you please take an example?

No, I've meant high memory limit available in the memcg v2 interface:
Documentation/admin-guide/cgroup-v2.rst.
-- 
Michal Hocko
SUSE Labs