public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] sched: move content out of core files for load average
Date: Fri, 19 Apr 2013 12:58:55 +0200	[thread overview]
Message-ID: <20130419105855.GA30060@gmail.com> (raw)
In-Reply-To: <1366368694.19383.22.camel@laptop>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Fri, 2013-04-19 at 10:25 +0200, Ingo Molnar wrote:
> > It might eventually make sense to integrate the 'average load'
> > calculation as well 
> > with all this - as they really have a similar purpose, the avenload[]
> > vector of 
> > averages is conceptually similar to the rq->cpu_load[] vector of
> > averages.
> 
> The /proc/loadavg definition isn't useful for anything remotely sane
> wrt load-balancing or otherwise, so I don't really see that integration
> happening (its a measure of how many tasks are blocked, where the
> load-balancer needs a measure of how many tasks are wanting to run).

Well, loadavg also includes running tasks:

        nr_active = this_rq->nr_running;
        nr_active += (long) this_rq->nr_uninterruptible;

but yeah, the two are not the same. It could at least integrate in terms 
of averaging code, working on two different instances of data structures - 
but yeah, full integration is indeed not possible.

Thanks,

	Ingo

  reply	other threads:[~2013-04-19 10:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13  0:04 [RFC PATCH 0/2] sched: move content out of core files for load average Paul Gortmaker
2013-04-13  0:04 ` [PATCH 1/2] sched: fork load calculation code from sched/core --> sched/load_avg Paul Gortmaker
2013-04-13  0:04 ` [PATCH 2/2] sched: move update_load_[add/sub/set] from sched.h to fair.c Paul Gortmaker
2013-04-13  4:30 ` [RFC PATCH 0/2] sched: move content out of core files for load average Rakib Mullick
2013-04-14  0:06   ` Paul Gortmaker
2013-04-15  9:33 ` Ingo Molnar
2013-04-18 11:14   ` Peter Zijlstra
2013-04-18 15:54     ` Paul Gortmaker
2013-04-18 17:06       ` Rakib Mullick
2013-04-18 23:13         ` Paul Gortmaker
2013-04-18 23:43           ` Paul Turner
2013-04-19  2:17             ` Charles Wang
2013-04-19  6:13           ` Rakib Mullick
2013-04-19  8:25       ` Ingo Molnar
2013-04-19 10:51         ` Peter Zijlstra
2013-04-19 10:58           ` Ingo Molnar [this message]
2013-04-19 17:05         ` Rakib Mullick
2013-04-21  8:54           ` Ingo Molnar

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=20130419105855.GA30060@gmail.com \
    --to=mingo@kernel.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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