[PATCH v3] 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 o

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

2020-09-15 Thread Chunxin Zang
On Tue, Sep 15, 2020 at 8:13 PM Michal Hocko wrote: > > On Tue 15-09-20 19:40:01, 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 > > consider

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

2020-09-15 Thread Michal Hocko
On Tue 15-09-20 19:40:01, 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