Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-04 Thread Yang Shi
On 1/4/19 2:57 PM, Yang Shi wrote: On 1/4/19 12:03 PM, Greg Thelen wrote: Yang Shi wrote: On 1/3/19 11:23 AM, Michal Hocko wrote: On Thu 03-01-19 11:10:00, Yang Shi wrote: On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: On 1/3/19 10:13 AM, Michal

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-04 Thread Yang Shi
On 1/4/19 12:03 PM, Greg Thelen wrote: Yang Shi wrote: On 1/3/19 11:23 AM, Michal Hocko wrote: On Thu 03-01-19 11:10:00, Yang Shi wrote: On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: On 1/3/19 10:13 AM, Michal Hocko wrote: [...] Is there any reason

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-04 Thread Yang Shi
On 1/4/19 12:03 PM, Greg Thelen wrote: Yang Shi wrote: On 1/3/19 11:23 AM, Michal Hocko wrote: On Thu 03-01-19 11:10:00, Yang Shi wrote: On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: On 1/3/19 10:13 AM, Michal Hocko wrote: [...] Is there any reason

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-04 Thread Greg Thelen
Yang Shi wrote: > On 1/3/19 11:23 AM, Michal Hocko wrote: >> On Thu 03-01-19 11:10:00, Yang Shi wrote: >>> >>> On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: > On 1/3/19 10:13 AM, Michal Hocko wrote: >> [...] >> Is there any reason for your scripts

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-04 Thread Yang Shi
On 1/4/19 12:55 AM, Michal Hocko wrote: On Thu 03-01-19 20:15:30, Yang Shi wrote: On 1/3/19 12:01 PM, Michal Hocko wrote: On Thu 03-01-19 11:49:32, Yang Shi wrote: On 1/3/19 11:23 AM, Michal Hocko wrote: On Thu 03-01-19 11:10:00, Yang Shi wrote: On 1/3/19 10:53 AM, Michal Hocko wrote:

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-04 Thread Michal Hocko
On Thu 03-01-19 20:15:30, Yang Shi wrote: > > > On 1/3/19 12:01 PM, Michal Hocko wrote: > > On Thu 03-01-19 11:49:32, Yang Shi wrote: > > > > > > On 1/3/19 11:23 AM, Michal Hocko wrote: > > > > On Thu 03-01-19 11:10:00, Yang Shi wrote: > > > > > On 1/3/19 10:53 AM, Michal Hocko wrote: > > > > >

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Yang Shi
On 1/3/19 12:01 PM, Michal Hocko wrote: On Thu 03-01-19 11:49:32, Yang Shi wrote: On 1/3/19 11:23 AM, Michal Hocko wrote: On Thu 03-01-19 11:10:00, Yang Shi wrote: On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: On 1/3/19 10:13 AM, Michal Hocko wrote:

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Michal Hocko
On Thu 03-01-19 11:49:32, Yang Shi wrote: > > > On 1/3/19 11:23 AM, Michal Hocko wrote: > > On Thu 03-01-19 11:10:00, Yang Shi wrote: > > > > > > On 1/3/19 10:53 AM, Michal Hocko wrote: > > > > On Thu 03-01-19 10:40:54, Yang Shi wrote: > > > > > On 1/3/19 10:13 AM, Michal Hocko wrote: > > [...]

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Yang Shi
On 1/3/19 11:23 AM, Michal Hocko wrote: On Thu 03-01-19 11:10:00, Yang Shi wrote: On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: On 1/3/19 10:13 AM, Michal Hocko wrote: [...] Is there any reason for your scripts to be strictly sequential here? In other

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Michal Hocko
On Thu 03-01-19 11:10:00, Yang Shi wrote: > > > On 1/3/19 10:53 AM, Michal Hocko wrote: > > On Thu 03-01-19 10:40:54, Yang Shi wrote: > > > > > > On 1/3/19 10:13 AM, Michal Hocko wrote: [...] > > > > Is there any reason for your scripts to be strictly sequential here? In > > > > other words why

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Yang Shi
On 1/3/19 10:53 AM, Michal Hocko wrote: On Thu 03-01-19 10:40:54, Yang Shi wrote: On 1/3/19 10:13 AM, Michal Hocko wrote: On Thu 03-01-19 09:33:14, Yang Shi wrote: On 1/3/19 2:12 AM, Michal Hocko wrote: On Thu 03-01-19 04:05:30, Yang Shi wrote: Currently, force empty reclaims memory

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Michal Hocko
On Thu 03-01-19 10:40:54, Yang Shi wrote: > > > On 1/3/19 10:13 AM, Michal Hocko wrote: > > On Thu 03-01-19 09:33:14, Yang Shi wrote: > > > > > > On 1/3/19 2:12 AM, Michal Hocko wrote: > > > > On Thu 03-01-19 04:05:30, Yang Shi wrote: > > > > > Currently, force empty reclaims memory

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Yang Shi
On 1/3/19 10:13 AM, Michal Hocko wrote: On Thu 03-01-19 09:33:14, Yang Shi wrote: On 1/3/19 2:12 AM, Michal Hocko wrote: On Thu 03-01-19 04:05:30, Yang Shi wrote: Currently, force empty reclaims memory synchronously when writing to memory.force_empty. It may take some time to return and

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Michal Hocko
On Thu 03-01-19 09:33:14, Yang Shi wrote: > > > On 1/3/19 2:12 AM, Michal Hocko wrote: > > On Thu 03-01-19 04:05:30, Yang Shi wrote: > > > Currently, force empty reclaims memory synchronously when writing to > > > memory.force_empty. It may take some time to return and the afterwards > > >

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Yang Shi
On 1/3/19 2:12 AM, Michal Hocko wrote: On Thu 03-01-19 04:05:30, Yang Shi wrote: Currently, force empty reclaims memory synchronously when writing to memory.force_empty. It may take some time to return and the afterwards operations are blocked by it. Although it can be interrupted by

Re: [RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-03 Thread Michal Hocko
On Thu 03-01-19 04:05:30, Yang Shi wrote: > > Currently, force empty reclaims memory synchronously when writing to > memory.force_empty. It may take some time to return and the afterwards > operations are blocked by it. Although it can be interrupted by signal, > it still seems suboptimal. Why

[RFC PATCH 0/3] mm: memcontrol: delayed force empty

2019-01-02 Thread Yang Shi
Currently, force empty reclaims memory synchronously when writing to memory.force_empty. It may take some time to return and the afterwards operations are blocked by it. Although it can be interrupted by signal, it still seems suboptimal. Now css offline is handled by worker, and the typical