From: Peter Zijlstra <peterz@infradead.org>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 3/6] sched: don't consider other cpus in our group in case of NEWLY_IDLE
Date: Mon, 22 Apr 2013 13:59:47 +0200 [thread overview]
Message-ID: <1366631987.4443.12.camel@laptop> (raw)
In-Reply-To: <1364277700-7509-4-git-send-email-iamjoonsoo.kim@lge.com>
On Tue, 2013-03-26 at 15:01 +0900, Joonsoo Kim wrote:
> Commit 88b8dac0 makes load_balance() consider other cpus in its group,
> regardless of idle type. When we do NEWLY_IDLE balancing, we should not
> consider it, because a motivation of NEWLY_IDLE balancing is to turn
> this cpu to non idle state if needed. This is not the case of other cpus.
> So, change code not to consider other cpus for NEWLY_IDLE balancing.
>
> With this patch, assign 'if (pulled_task) this_rq->idle_stamp = 0'
> in idle_balance() is corrected, because NEWLY_IDLE balancing doesn't
> consider other cpus. Assigning to 'this_rq->idle_stamp' is now valid.
>
> Cc: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 9d693d0..3f8c4f2 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -5007,8 +5007,17 @@ static int load_balance(int this_cpu, struct rq *this_rq,
> .cpus = cpus,
> };
>
> + /* For NEWLY_IDLE load_balancing, we don't need to consider
> + * other cpus in our group */
> + if (idle == CPU_NEWLY_IDLE) {
> + env.dst_grpmask = NULL;
> + /* we don't care max_lb_iterations in this case,
> + * in following patch, this will be removed */
This comment violates coding style; comments looks like:
/* this is a single-line comment */
or
/*
* this is a multi-
* line comment.
*/
Luckily you're deleting these offensive lines again in patch 6 :-)
> + max_lb_iterations = 0;
> + } else {
> + max_lb_iterations = cpumask_weight(env.dst_grpmask);
> + }
> cpumask_copy(cpus, cpu_active_mask);
> - max_lb_iterations = cpumask_weight(env.dst_grpmask);
>
> schedstat_inc(sd, lb_count[idle]);
>
next prev parent reply other threads:[~2013-04-22 11:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 6:01 [PATCH v2 0/6] correct load_balance() Joonsoo Kim
2013-03-26 6:01 ` [PATCH v2 1/6] sched: change position of resched_cpu() in load_balance() Joonsoo Kim
2013-03-26 6:01 ` [PATCH v2 2/6] sched: explicitly cpu_idle_type checking in rebalance_domains() Joonsoo Kim
2013-04-22 11:59 ` Peter Zijlstra
2013-03-26 6:01 ` [PATCH v2 3/6] sched: don't consider other cpus in our group in case of NEWLY_IDLE Joonsoo Kim
2013-04-22 11:59 ` Peter Zijlstra [this message]
2013-03-26 6:01 ` [PATCH v2 4/6] sched: move up affinity check to mitigate useless redoing overhead Joonsoo Kim
2013-03-26 6:01 ` [PATCH v2 5/6] sched: rename load_balance_tmpmask to load_balance_mask Joonsoo Kim
2013-03-26 6:01 ` [PATCH v2 6/6] sched: prevent to re-select dst-cpu in load_balance() Joonsoo Kim
2013-04-22 11:59 ` Peter Zijlstra
2013-04-22 8:01 ` [PATCH v2 0/6] correct load_balance() Joonsoo Kim
2013-04-22 12:01 ` Peter Zijlstra
2013-04-22 20:07 ` Davidlohr Bueso
2013-04-23 8:31 ` Joonsoo Kim
2013-04-23 8:50 ` Joonsoo Kim
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=1366631987.4443.12.camel@laptop \
--to=peterz@infradead.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vatsa@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.