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
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
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
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
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%
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%
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:
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:
8 matches
Mail list logo