Re: [PATCH] sched/fair: refine maximum periods for decay_load

On 5 August 2016 at 10:17, Leo Yan wrote: > Hi Vincent, > > Thanks for review. > > On Fri, Aug 05, 2016 at 09:56:46AM +0200, Vincent Guittot wrote: >> Hi Leo, >> >> On 5 August 2016 at 08:34, Leo Yan wrote: >> > >> > In current code, decay_load() will consider to set load value to zero >> > after

Re: [PATCH] sched/fair: refine maximum periods for decay_load

Hi Vincent, Thanks for review. On Fri, Aug 05, 2016 at 09:56:46AM +0200, Vincent Guittot wrote: > Hi Leo, > > On 5 August 2016 at 08:34, Leo Yan wrote: > > > > In current code, decay_load() will consider to set load value to zero > > after passing 32*64 ms. So this means max_load * (0.5^64) ~=

Re: [PATCH] sched/fair: refine maximum periods for decay_load

Hi Leo, On 5 August 2016 at 08:34, Leo Yan wrote: > > In current code, decay_load() will consider to set load value to zero > after passing 32*64 ms. So this means max_load * (0.5^64) ~= 0. > > Kernel can support maximum number of processes and threads to 2^29 and > set task with highest priority

[PATCH] sched/fair: refine maximum periods for decay_load

In current code, decay_load() will consider to set load value to zero after passing 32*64 ms. So this means max_load * (0.5^64) ~= 0. Kernel can support maximum number of processes and threads to 2^29 and set task with highest priority with nice=-20 (weight = 88761). So in worst case, one CPU may