public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
	mingo@kernel.org, pjt@google.com, rostedt@goodmis.org,
	fweisbec@gmail.com, efault@gmx.de
Subject: Re: [PATCH Resend v6] sched: fix wrong rq's runnable_avg update with rt tasks
Date: Fri, 19 Apr 2013 13:47:16 +0200	[thread overview]
Message-ID: <1366372036.24945.1.camel@laptop> (raw)
In-Reply-To: <1366302867-5055-1-git-send-email-vincent.guittot@linaro.org>

On Thu, 2013-04-18 at 18:34 +0200, Vincent Guittot wrote:
> The current update of the rq's load can be erroneous when RT tasks are
> involved
> 
> The update of the load of a rq that becomes idle, is done only if the avg_idle
> is less than sysctl_sched_migration_cost. If RT tasks and short idle duration
> alternate, the runnable_avg will not be updated correctly and the time will be
> accounted as idle time when a CFS task wakes up.
> 
> A new idle_enter function is called when the next task is the idle function
> so the elapsed time will be accounted as run time in the load of the rq,
> whatever the average idle time is. The function update_rq_runnable_avg is
> removed from idle_balance.
> 
> When a RT task is scheduled on an idle CPU, the update of the rq's load is
> not done when the rq exit idle state because CFS's functions are not
> called. Then, the idle_balance, which is called just before entering the
> idle function, updates the rq's load and makes the assumption that the
> elapsed time since the last update, was only running time.
> 
> As a consequence, the rq's load of a CPU that only runs a periodic RT task,
> is close to LOAD_AVG_MAX whatever the running duration of the RT task is.
> 
> A new idle_exit function is called when the prev task is the idle function
> so the elapsed time will be accounted as idle time in the rq's load.

Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>

Thanks Vince!


  parent reply	other threads:[~2013-04-19 11:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 16:34 [PATCH Resend v6] sched: fix wrong rq's runnable_avg update with rt tasks Vincent Guittot
2013-04-19  4:30 ` Mike Galbraith
2013-04-19  7:49   ` Vincent Guittot
2013-04-19  8:14     ` Mike Galbraith
2013-04-19  8:50       ` Vincent Guittot
2013-04-19  9:21         ` Mike Galbraith
2013-04-19  9:37           ` Mike Galbraith
2013-04-19 11:11           ` Vincent Guittot
2013-04-19 11:47 ` Peter Zijlstra [this message]
2013-04-19 21:28 ` Steven Rostedt
2013-04-21 12:52 ` [tip:sched/core] sched: Fix wrong rq' s " tip-bot for Vincent Guittot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1366372036.24945.1.camel@laptop \
    --to=peterz@infradead.org \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pjt@google.com \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox