From: Alex Shi <alex.shi@linaro.org>
To: mingo@redhat.com, peterz@infradead.org, morten.rasmussen@arm.com,
vincent.guittot@linaro.org, daniel.lezcano@linaro.org
Cc: wangyun@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Alex Shi <alex.shi@linaro.org>, Mike Galbraith <efault@gmx.de>
Subject: Re: [RFC PATCH] sched: select_idle_sibling macro optimize
Date: Thu, 16 Jan 2014 21:13:25 +0800 [thread overview]
Message-ID: <52D7DAF5.4020506@linaro.org> (raw)
In-Reply-To: <1389795808-32013-1-git-send-email-alex.shi@linaro.org>
Add Mike Galbraith.
Any one like to give some comments?
On 01/15/2014 10:23 PM, Alex Shi wrote:
> If the sd domain just has one group, then we must be caught the
> i == target later, and then goes to deeper level domain.
> So just skip this domain checking to save some instructions.
>
> Signed-off-by: Alex Shi <alex.shi@linaro.org>
> ---
> kernel/sched/fair.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index c7395d9..3265fbc 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -4196,6 +4196,11 @@ static int select_idle_sibling(struct task_struct *p, int target)
> sd = rcu_dereference(per_cpu(sd_llc, target));
> for_each_lower_domain(sd) {
> sg = sd->groups;
> +
> + /* skip single group domain */
> + if (sg == sg->next)
> + continue;
> +
> do {
> if (!cpumask_intersects(sched_group_cpus(sg),
> tsk_cpus_allowed(p)))
>
--
Thanks
Alex
next prev parent reply other threads:[~2014-01-16 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 14:23 [RFC PATCH] sched: select_idle_sibling macro optimize Alex Shi
2014-01-16 13:13 ` Alex Shi [this message]
2014-01-16 13:52 ` Mike Galbraith
2014-01-17 2:14 ` Alex Shi
2014-01-17 3:15 ` Michael wang
2014-01-17 3:36 ` Mike Galbraith
2014-01-17 5:40 ` 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=52D7DAF5.4020506@linaro.org \
--to=alex.shi@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).