All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, morten.rasmussen@arm.com,
	vincent.guittot@linaro.org, daniel.lezcano@linaro.org,
	fweisbec@gmail.com, linux@arm.linux.org.uk, tony.luck@intel.com,
	fenghua.yu@intel.com, tglx@linutronix.de,
	akpm@linux-foundation.org, arjan@linux.intel.com, pjt@google.com,
	fengguang.wu@intel.com, james.hogan@imgtec.com,
	jason.low2@hp.com, gregkh@linuxfoundation.org,
	hanjun.guo@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] sched: remove cpu_load decay
Date: Sat, 14 Dec 2013 21:27:59 +0800	[thread overview]
Message-ID: <52AC5CDF.8050209@linaro.org> (raw)
In-Reply-To: <20131213200303.GI2480@laptop.programming.kicks-ass.net>

On 12/14/2013 04:03 AM, Peter Zijlstra wrote:
> 
> 
> I had a quick peek at the actual patches.
> 
> afaict we're now using weighted_cpuload() aka runnable_load_avg as the
> ->cpu_load. Whatever happened to also using the blocked_avg?

When enabling the sched_avg in load balance, I didn't find any positive
testing result for several blocked_avg trying, just few regression. :(

And since this patchset is almost clean up only, no blocked_load_avg
trying again...

> 
> I totally hate patch 4; it seems like a random hack to make up for the
> lack of blocked_avg.

Yes, this bias criteria seems a bit arbitrary. :)
But, anyway even with blocked_load_avg, we still need to consider to
bias to local cpu. like in a scenario, 2 cpus both has nearly zero
blocked_load_avg.

BTW,

Paul, do you has new idea on blocked_load_avg using?

-- 
Thanks
    Alex

  reply	other threads:[~2013-12-14 13:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  9:05 [PATCH 0/4] sched: remove cpu_load decay Alex Shi
2013-12-03  9:05 ` [PATCH 1/4] sched: shortcut to remove load_idx Alex Shi
2013-12-03  9:05 ` [PATCH 2/4] sched: remove rq->cpu_load[load_idx] array Alex Shi
2013-12-03  9:05 ` [PATCH 3/4] sched: clean up cpu_load update Alex Shi
2013-12-03  9:05 ` [PATCH 4/4] sched: bias to target cpu load to reduce task moving Alex Shi
2013-12-04  9:06   ` Yuanhan Liu
2013-12-04 11:25     ` Alex Shi
2013-12-17 14:10   ` Morten Rasmussen
2013-12-17 15:38     ` Peter Zijlstra
2013-12-19 13:34       ` Alex Shi
2013-12-20 11:19         ` Morten Rasmussen
2013-12-20 14:45           ` Alex Shi
2013-12-25 14:58           ` Alex Shi
2014-01-02 16:04             ` Morten Rasmussen
2014-01-06 13:35               ` Alex Shi
2014-01-07 12:55                 ` Morten Rasmussen
2014-01-07 12:59                   ` Peter Zijlstra
2014-01-07 13:15                     ` Peter Zijlstra
2014-01-07 13:32                       ` Vincent Guittot
2014-01-07 13:40                         ` Peter Zijlstra
2014-01-07 15:16                       ` Morten Rasmussen
2014-01-07 20:37                         ` Peter Zijlstra
2014-01-08 14:15                     ` Alex Shi
2013-12-03 10:26 ` [PATCH 0/4] sched: remove cpu_load decay Peter Zijlstra
2013-12-10  1:04   ` Alex Shi
2013-12-10  1:06     ` Paul Turner
2013-12-13 19:50     ` bsegall
2013-12-14 12:53       ` Alex Shi
2013-12-13 20:03 ` Peter Zijlstra
2013-12-14 13:27   ` Alex Shi [this message]
2013-12-17 14:04     ` Morten Rasmussen
2013-12-17 15:37       ` Peter Zijlstra
2013-12-17 18:12         ` Morten Rasmussen
2013-12-20 14:43           ` Alex Shi

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=52AC5CDF.8050209@linaro.org \
    --to=alex.shi@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=fengguang.wu@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hanjun.guo@linaro.org \
    --cc=james.hogan@imgtec.com \
    --cc=jason.low2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.