tick-sched: Update nohz load even if tick already stopped
PATCH 1/1 tick-sched: Update nohz load even if tick already stopped
The way loadavg is tracked during nohz only pays attention to the load upon entering nohz. This can be particularly noticeable if nohz is entered while non-idle, and then the cpu goes idle and stays that way for a long time. We've had reports of a loadavg near 150 on a mostly idle system.
Calling calc_load_nohz_start() regardless of whether the tick is already stopped addresses the issue when going idle. Tracking load changes when not going idle (e.g. multiple SCHED_FIFO tasks coming and going) is not addressed by this patch.
--- kernel/time/tick-sched.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
kernel/time/tick-sched.c +3 -1
@@ -763,6 +763,9 @@ static void tick_nohz_stop_tick(struct tick_sched *ts, int cpu) ts->do_timer_last =0 ; } +/* Even if the tick was already stopped, load may have changed */ +calc_load_nohz_start (); +/* Skip reprogram of event if its not changed */ if (ts->tick_stopped && (expires == ts->next_tick)) {/* Sanity check: make sure clockevent is actually programmed */
@@ -783,7 +786,6 @@ static void tick_nohz_stop_tick(struct tick_sched *ts, int cpu)* the scheduler tick in nohz_restart_sched_tick. */ if (!ts->tick_stopped) { -calc_load_nohz_start ();quiet_vmstat (); ts->last_tick =hrtimer_get_expires (&ts->sched_timer);
Signature · 1 line
1.8.3.1
Frederic Weisbecker
maintainerQuoted 31 lines · Scott Wood
The way loadavg is tracked during nohz only pays attention to the load upon entering nohz. This can be particularly noticeable if nohz is entered while non-idle, and then the cpu goes idle and stays that way for a long time. We've had reports of a loadavg near 150 on a mostly idle system.
Calling
calc_load_nohz_start()regardless of whether the tick is already stopped addresses the issue when going idle. Tracking load changes when not going idle (e.g. multipleSCHED_FIFOtasks coming and going) is not addressed by this patch.Signed-off-by Scott Wood <[email protected]>--- kernel/time/tick-sched.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)kernel/time/tick-sched.c +3
-0@@ -763,6 +763,9 @@ static void tick_nohz_stop_tick(struct tick_sched *ts, int cpu) ts->do_timer_last =0 ; } +/* Even if the tick was already stopped, load may have changed */ +calc_load_nohz_start (); +/* Skip reprogram of event if its not changed */ if (ts->tick_stopped && (expires == ts->next_tick)) {/* Sanity check: make sure clockevent is actually programmed */
kernel/time/tick-sched.c static void tick_nohz_stop_tick(struct tick_sched *ts, int cpu) · line 791
Quoted 7 lines
kernel/time/tick-sched.c +0
-1@@ -783,7 +786,6 @@ static void tick_nohz_stop_tick(struct tick_sched *ts, int cpu)* the scheduler tick in nohz_restart_sched_tick. */ if (!ts->tick_stopped) { -calc_load_nohz_start ();quiet_vmstat (); ts->last_tick =hrtimer_get_expires (&ts->sched_timer);
Thanks. I've pondered over your patch to try to avoid calling calc_load_nohz_start() unconditionally like that. But in the end the fast path of this function shouldn't bring much overhead and does pretty much the same as what I would do to call it conditionally.
So I'm applying it.