Thread (11 messages) 11 messages, 3 authors, 2020-08-03

Re: [PATCH] mm, memcg: do full scan initially in force_empty

From: Michal Hocko <mhocko@suse.com>
Date: 2020-08-03 14:37:13

On Mon 03-08-20 22:26:10, Yafang Shao wrote:
On Mon, Aug 3, 2020 at 10:18 PM Yafang Shao [off-list ref] wrote:
[...]
quoted
You can use memcg limits (e.g. memory high) to pro-actively reclaim
excess memory. Have you tried that?
The memcg limit not only reclaim the slabs, but also reclaim the pagecaches.
True but drop_cache doesn't distinguish different kind of objects
either. The reclaim will simply try to drop unused cache. All or nothing
behavior of drop_caches is exactly what I dislike about the interface.
Memory reclaim can at least consider age and reflect the general usage
pattern.
Furthermore, there is no per-memcg vm.vfs_cache_pressure neither.
Why does that matter?

-- 
Michal Hocko
SUSE Labs
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help