Re: [PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-25 Thread Michal Hocko
On Wed 25-01-17 11:03:53, hejianet wrote: > > > On 25/01/2017 12:54 AM, Michal Hocko wrote: > > On Tue 24-01-17 15:49:03, Jia He wrote: > > > Currently there is no hard limitation for kswapd retry times if no > > > progress > > > is made. > > > > Yes, because the main objective of the kswapd

Re: [PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-25 Thread Michal Hocko
On Wed 25-01-17 11:03:53, hejianet wrote: > > > On 25/01/2017 12:54 AM, Michal Hocko wrote: > > On Tue 24-01-17 15:49:03, Jia He wrote: > > > Currently there is no hard limitation for kswapd retry times if no > > > progress > > > is made. > > > > Yes, because the main objective of the kswapd

Re: [PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-24 Thread hejianet
On 25/01/2017 12:54 AM, Michal Hocko wrote: On Tue 24-01-17 15:49:03, Jia He wrote: Currently there is no hard limitation for kswapd retry times if no progress is made. Yes, because the main objective of the kswapd is to balance all memory zones. So having a hard limit on retries doesn't

Re: [PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-24 Thread hejianet
On 25/01/2017 12:54 AM, Michal Hocko wrote: On Tue 24-01-17 15:49:03, Jia He wrote: Currently there is no hard limitation for kswapd retry times if no progress is made. Yes, because the main objective of the kswapd is to balance all memory zones. So having a hard limit on retries doesn't

Re: [PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-24 Thread Michal Hocko
On Tue 24-01-17 15:49:03, Jia He wrote: > Currently there is no hard limitation for kswapd retry times if no progress > is made. Yes, because the main objective of the kswapd is to balance all memory zones. So having a hard limit on retries doesn't make any sense. > Then kswapd will take 100%

Re: [PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-24 Thread Michal Hocko
On Tue 24-01-17 15:49:03, Jia He wrote: > Currently there is no hard limitation for kswapd retry times if no progress > is made. Yes, because the main objective of the kswapd is to balance all memory zones. So having a hard limit on retries doesn't make any sense. > Then kswapd will take 100%

[PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-23 Thread Jia He
Currently there is no hard limitation for kswapd retry times if no progress is made. Then kswapd will take 100% for a long time. In my test, I tried to allocate 4000 hugepages by: echo 4000 > /proc/sys/vm/nr_hugepages Then,kswapd will take 100% cpu for a long time. The numa layout is:

[PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

2017-01-23 Thread Jia He
Currently there is no hard limitation for kswapd retry times if no progress is made. Then kswapd will take 100% for a long time. In my test, I tried to allocate 4000 hugepages by: echo 4000 > /proc/sys/vm/nr_hugepages Then,kswapd will take 100% cpu for a long time. The numa layout is: