Re: [PATCH v5] mm/vmscan: add a fatal signals check in drop_slab_node

2020-09-16 Thread David Hildenbrand
On 16.09.20 04:53, zangchun...@bytedance.com wrote: > From: Chunxin Zang > > On our server, there are about 10k memcg in one machine. They use memory > very frequently. We have observed that drop_caches can take a > considerable amount of time, and can't stop it. > > There are two reasons: > 1.

Re: [PATCH v5] mm/vmscan: add a fatal signals check in drop_slab_node

2020-09-16 Thread Chris Down
zangchun...@bytedance.com writes: From: Chunxin Zang On our server, there are about 10k memcg in one machine. They use memory very frequently. We have observed that drop_caches can take a considerable amount of time, and can't stop it. There are two reasons: 1. There is somebody constantly gen

Re: [PATCH v5] mm/vmscan: add a fatal signals check in drop_slab_node

2020-09-15 Thread Michal Hocko
On Wed 16-09-20 10:53:59, zangchun...@bytedance.com wrote: > From: Chunxin Zang > > On our server, there are about 10k memcg in one machine. They use memory > very frequently. We have observed that drop_caches can take a > considerable amount of time, and can't stop it. > > There are two reasons

[PATCH v5] mm/vmscan: add a fatal signals check in drop_slab_node

2020-09-15 Thread zangchunxin
From: Chunxin Zang On our server, there are about 10k memcg in one machine. They use memory very frequently. We have observed that drop_caches can take a considerable amount of time, and can't stop it. There are two reasons: 1. There is somebody constantly generating more objects to reclaim on