From: Alex Shi <alex.shi@linaro.org>
To: Morten Rasmussen <morten.rasmussen@arm.com>,
Fengguang Wu <fengguang.wu@intel.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"efault@gmx.de" <efault@gmx.de>,
"wangyun@linux.vnet.ibm.com" <wangyun@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mgorman@suse.de" <mgorman@suse.de>
Subject: Re: [RESEND PATCH V5 0/8] remove cpu_load idx
Date: Tue, 06 May 2014 16:33:38 +0800 [thread overview]
Message-ID: <53689E62.9090403@linaro.org> (raw)
In-Reply-To: <5360C15B.9060608@linaro.org>
>
> Maybe the predication is reasonable on per task history. but on a cpu
> load history, with many tasks rebalance. No testing show current method
> is helpful.
>
> For task load change, scheduler has no idea for its future except guess
> from its history. but for cpu load change, scheduler know this from task
> wakeup and balance, which both under control and its aim.
>
>
> I think the first patch of this serial has the same effect of LB_LIAS
> disable. and previous result show performance is good.
>
> Anyway, I just pushed the following patch to github, maybe fengguang's
> testing system will care this.
Fengguang,
Are there any performance change on
https://github.com/alexshi/power-scheduling.git noload repository?
>
> diff --git a/kernel/sched/features.h b/kernel/sched/features.h
> index 5716929..0bf649f 100644
> --- a/kernel/sched/features.h
> +++ b/kernel/sched/features.h
> @@ -43,7 +43,7 @@ SCHED_FEAT(ARCH_POWER, true)
>
> SCHED_FEAT(HRTICK, false)
> SCHED_FEAT(DOUBLE_TICK, false)
> -SCHED_FEAT(LB_BIAS, true)
> +SCHED_FEAT(LB_BIAS, false)
>
>
--
Thanks
Alex
next prev parent reply other threads:[~2014-05-06 8:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 2:43 [RESEND PATCH V5 0/8] remove cpu_load idx Alex Shi
2014-04-16 2:43 ` [PATCH V5 1/8] sched: shortcut to remove load_idx Alex Shi
2014-04-16 2:43 ` [PATCH V5 2/8] sched: remove rq->cpu_load[load_idx] array Alex Shi
2014-04-16 2:43 ` [PATCH V5 3/8] sched: remove source_load and target_load Alex Shi
2014-04-24 14:18 ` Peter Zijlstra
2014-04-16 2:43 ` [PATCH V5 4/8] sched: remove LB_BIAS Alex Shi
2014-04-16 2:43 ` [PATCH V5 5/8] sched: clean up cpu_load update Alex Shi
2014-04-16 2:43 ` [PATCH V5 6/8] sched: rewrite update_cpu_load_nohz Alex Shi
2014-04-16 2:43 ` [PATCH V5 7/8] sched: remove rq->cpu_load and rq->nr_load_updates Alex Shi
2014-04-16 2:43 ` [PATCH V5 8/8] sched: rename update_*_cpu_load Alex Shi
2014-04-24 16:20 ` [RESEND PATCH V5 0/8] remove cpu_load idx Peter Zijlstra
2014-04-29 15:04 ` Morten Rasmussen
2014-05-09 16:30 ` Alex Shi
2014-05-01 0:41 ` Alex Shi
2014-05-06 9:54 ` Preeti Murthy
2014-05-06 11:39 ` Peter Zijlstra
2014-05-08 9:10 ` Preeti U Murthy
2014-04-29 14:52 ` Morten Rasmussen
2014-04-30 9:24 ` Alex Shi
2014-05-06 8:33 ` Alex Shi [this message]
2014-05-06 11:43 ` Peter Zijlstra
2014-05-09 16:41 ` 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=53689E62.9090403@linaro.org \
--to=alex.shi@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=efault@gmx.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=wangyun@linux.vnet.ibm.com \
/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.