Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg

To: Michal Hocko <mhocko@xxxxxxxx>
Subject: Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
From: Neil Sun <neilsun@xxxxxxxxxx>
Date: Tue, 6 Apr 2021 23:12:34 +0800
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <YGxyojApNhi5DjFc@dhcp22.suse.cz>
References: <1617359934-7812-1-git-send-email-neilsun@yunify.com> <YGwMD3DOymOFJ7O5@dhcp22.suse.cz> <4dba277d-e497-5c34-0e68-fd2283585de2@yunify.com> <YGxIVDXw7wtBytIg@dhcp22.suse.cz> <d21f3b10-0c39-211f-dc45-e81c8da5dd9d@yunify.com> <YGxyojApNhi5DjFc@dhcp22.suse.cz>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.0



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?

--
Neil

Follow-Ups:
- Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Michal Hocko

References:
- [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Neil Sun
- Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Michal Hocko
- Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Neil Sun
- Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Michal Hocko
- Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Neil Sun
- Re: [PATCH] mm/vmscan.c: drop_slab_node with task's memcg
  - From: Michal Hocko