[lkml]   [2014]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [NOHZ] Remove scheduler_tick_max_deferment
On Mon, 10 Nov 2014, Viresh Kumar wrote:

> On 6 November 2014 22:54, Christoph Lameter <> wrote:
> > We did not need to housekeeper in the dynticks idle case. What is so
> > different about dynticks busy?
> We do have a running task here and so the stats are important..

The task is running in user space only and if there is any important
kernel action the tick will be coming on. Stats are not that important and
predictable I would say.

We could add stuff to the vmstat kworker thread to check for activity that
requires updates.

> > I may not have the complete picture of the timer tick processing in my
> > mind these days (it has been a lots of years since I did any work there
> > after all) but as far as my arguably simplistic reading of the code goes I
> > do not see why a housekeeper would be needed there. The load is constant
> > and known in the dynticks busy case as it is in the dynticks idle case.
> I tried to initiate a thread on similar stuff, might be helpful:

Hmmm... yes that is interesting. I agree that the process should be
exempted from load balancing since the idea of NOHZ is to lower OS noise
and load balancing would add significant amounts of noise.

NUMA balancing is also a source of noise and so we should have that off by
default as well.

 \ /
  Last update: 2014-11-10 17:41    [W:0.097 / U:2.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site