From: Namhyung Kim <namhyung@kernel.org>
To: Alex Shi <alex.shi@intel.com>
Cc: mingo@redhat.com, peterz@infradead.org, tglx@linutronix.de,
akpm@linux-foundation.org, arjan@linux.intel.com, bp@alien8.de,
pjt@google.com, efault@gmx.de, vincent.guittot@linaro.org,
gregkh@linuxfoundation.org, preeti@linux.vnet.ibm.com,
viresh.kumar@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [patch v6 13/21] sched: using avg_idle to detect bursty wakeup
Date: Wed, 03 Apr 2013 14:08:01 +0900 [thread overview]
Message-ID: <876204fbgu.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1364654108-16307-14-git-send-email-alex.shi@intel.com> (Alex Shi's message of "Sat, 30 Mar 2013 22:35:00 +0800")
Hi Alex,
On Sat, 30 Mar 2013 22:35:00 +0800, Alex Shi wrote:
> Sleeping task has no utiliation, when they were bursty waked up, the
> zero utilization make scheduler out of balance, like aim7 benchmark.
>
> rq->avg_idle is 'to used to accommodate bursty loads in a dirt simple
> dirt cheap manner' -- Mike Galbraith.
>
> With this cheap and smart bursty indicator, we can find the wake up
> burst, and use nr_running as instant utilization in this scenario.
>
> For other scenarios, we still use the precise CPU utilization to
> judage if a domain is eligible for power scheduling.
>
> Thanks for Mike Galbraith's idea!
>
> Signed-off-by: Alex Shi <alex.shi@intel.com>
> ---
> kernel/sched/fair.c | 33 ++++++++++++++++++++++++++-------
> 1 file changed, 26 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 83b2c39..ae07190 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -3371,12 +3371,19 @@ static unsigned int max_rq_util(int cpu)
> * Try to collect the task running number and capacity of the group.
> */
> static void get_sg_power_stats(struct sched_group *group,
> - struct sched_domain *sd, struct sg_lb_stats *sgs)
> + struct sched_domain *sd, struct sg_lb_stats *sgs, int burst)
> {
> int i;
>
> - for_each_cpu(i, sched_group_cpus(group))
> - sgs->group_util += max_rq_util(i);
> + for_each_cpu(i, sched_group_cpus(group)) {
> + struct rq *rq = cpu_rq(i);
> +
> + if (burst && rq->nr_running > 1)
> + /* use nr_running as instant utilization */
> + sgs->group_util += rq->nr_running;
I guess multiplying FULL_UTIL to rq->nr_running here will remove
special-casing the burst in is_sd_full(). Also moving this logic to
max_rq_util() looks better IMHO.
> + else
> + sgs->group_util += max_rq_util(i);
> + }
>
> sgs->group_weight = group->group_weight;
> }
> @@ -3390,6 +3397,8 @@ static int is_sd_full(struct sched_domain *sd,
> struct sched_group *group;
> struct sg_lb_stats sgs;
> long sd_min_delta = LONG_MAX;
> + int cpu = task_cpu(p);
> + int burst = 0;
> unsigned int putil;
>
> if (p->se.load.weight == p->se.avg.load_avg_contrib)
> @@ -3399,15 +3408,21 @@ static int is_sd_full(struct sched_domain *sd,
> putil = (u64)(p->se.avg.runnable_avg_sum << SCHED_POWER_SHIFT)
> / (p->se.avg.runnable_avg_period + 1);
>
> + if (cpu_rq(cpu)->avg_idle < sysctl_sched_burst_threshold)
> + burst = 1;
Sorry, I don't understand this.
Given that sysctl_sched_burst_threshold is twice of
sysctl_sched_migration_cost which is max value of rq->avg_idle, the
avg_idle will be almost always less than the threshold, right?
So how does it find out the burst case? I thought it's the case of a
cpu is in idle for a while and then wakes number of tasks at once. If
so, shouldn't it check whether the avg_idle is *longer* than certain
threshold? What am I missing?
Thanks,
Namhyung
> +
> /* Try to collect the domain's utilization */
> group = sd->groups;
> do {
> long g_delta;
>
> memset(&sgs, 0, sizeof(sgs));
> - get_sg_power_stats(group, sd, &sgs);
> + get_sg_power_stats(group, sd, &sgs, burst);
>
> - g_delta = sgs.group_weight * FULL_UTIL - sgs.group_util;
> + if (burst)
> + g_delta = sgs.group_weight - sgs.group_util;
> + else
> + g_delta = sgs.group_weight * FULL_UTIL - sgs.group_util;
>
> if (g_delta > 0 && g_delta < sd_min_delta) {
> sd_min_delta = g_delta;
> @@ -3417,8 +3432,12 @@ static int is_sd_full(struct sched_domain *sd,
> sds->sd_util += sgs.group_util;
> } while (group = group->next, group != sd->groups);
>
> - if (sds->sd_util + putil < sd->span_weight * FULL_UTIL)
> - return 0;
> + if (burst) {
> + if (sds->sd_util < sd->span_weight)
> + return 0;
> + } else
> + if (sds->sd_util + putil < sd->span_weight * FULL_UTIL)
> + return 0;
>
> /* can not hold one more task in this domain */
> return 1;
next prev parent reply other threads:[~2013-04-03 5:08 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 14:34 [patch v6 0/21] sched: power aware scheduling Alex Shi
2013-03-30 14:34 ` [patch v6 01/21] Revert "sched: Introduce temporary FAIR_GROUP_SCHED dependency for load-tracking" Alex Shi
2013-03-30 14:34 ` [patch v6 02/21] sched: set initial value of runnable avg for new forked task Alex Shi
2013-03-30 14:34 ` [patch v6 03/21] sched: only count runnable avg on cfs_rq's nr_running Alex Shi
2013-04-02 14:30 ` Vincent Guittot
2013-04-03 1:02 ` Alex Shi
2013-04-03 1:23 ` Paul Turner
2013-04-03 2:12 ` Alex Shi
2013-03-30 14:34 ` [patch v6 04/21] sched: add sched balance policies in kernel Alex Shi
2013-03-30 14:34 ` [patch v6 05/21] sched: add sysfs interface for sched_balance_policy selection Alex Shi
2013-03-30 14:34 ` [patch v6 06/21] sched: log the cpu utilization at rq Alex Shi
2013-03-30 14:34 ` [patch v6 07/21] sched: add new sg/sd_lb_stats fields for incoming fork/exec/wake balancing Alex Shi
2013-03-30 14:34 ` [patch v6 08/21] sched: move sg/sd_lb_stats struct ahead Alex Shi
2013-03-30 14:34 ` [patch v6 09/21] sched: scale_rt_power rename and meaning change Alex Shi
2013-03-30 14:34 ` [patch v6 10/21] sched: get rq potential maximum utilization Alex Shi
2013-04-02 9:02 ` Namhyung Kim
2013-04-02 13:38 ` Alex Shi
2013-04-03 2:15 ` Alex Shi
2013-04-03 2:22 ` Paul Turner
2013-04-03 2:35 ` Alex Shi
2013-04-03 8:07 ` Alex Shi
2013-04-02 14:38 ` Vincent Guittot
2013-04-03 1:11 ` Alex Shi
2013-03-30 14:34 ` [patch v6 11/21] sched: detect wakeup burst with rq->avg_idle Alex Shi
2013-04-03 8:12 ` Alex Shi
2013-03-30 14:34 ` [patch v6 12/21] sched: add power aware scheduling in fork/exec/wake Alex Shi
2013-04-01 9:50 ` Preeti U Murthy
2013-04-01 13:43 ` Alex Shi
2013-03-30 14:35 ` [patch v6 13/21] sched: using avg_idle to detect bursty wakeup Alex Shi
2013-04-03 5:08 ` Namhyung Kim [this message]
2013-04-03 5:41 ` Alex Shi
2013-04-03 8:10 ` Alex Shi
2013-03-30 14:35 ` [patch v6 14/21] sched: packing transitory tasks in wakeup power balancing Alex Shi
2013-03-30 14:35 ` [patch v6 15/21] sched: add power/performance balance allow flag Alex Shi
2013-03-30 14:35 ` [patch v6 16/21] sched: pull all tasks from source group Alex Shi
2013-03-30 14:35 ` [patch v6 17/21] sched: no balance for prefer_sibling in power scheduling Alex Shi
2013-03-30 14:35 ` [patch v6 18/21] sched: add new members of sd_lb_stats Alex Shi
2013-03-30 14:35 ` [patch v6 19/21] sched: power aware load balance Alex Shi
2013-03-30 14:35 ` [patch v6 20/21] sched: lazy power balance Alex Shi
2013-03-30 14:35 ` [patch v6 21/21] sched: don't do power balance on share cpu power domain Alex Shi
2013-04-01 5:05 ` [patch v6 0/21] sched: power aware scheduling Michael Wang
2013-04-01 6:17 ` Alex Shi
2013-04-01 6:20 ` Alex Shi
2013-04-03 8:17 ` Alex Shi
2013-04-04 0:57 ` 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=876204fbgu.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=preeti@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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
Powered by JetHome