From: tip-bot for Peter Zijlstra <peterz@infradead.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
efault@gmx.de, peterz@infradead.org, alex.shi@intel.com,
suresh.b.siddha@intel.com, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:sched/urgent] sched: Fix select_idle_sibling() regression in selecting an idle SMT sibling
Date: Fri, 16 Dec 2011 03:36:10 -0800 [thread overview]
Message-ID: <tip-ab2789213d224202237292d78aaa0c386c7b28b2@git.kernel.org> (raw)
In-Reply-To: <1323978421.1984.244.camel@sbsiddha-desk.sc.intel.com>
Commit-ID: ab2789213d224202237292d78aaa0c386c7b28b2
Gitweb: http://git.kernel.org/tip/ab2789213d224202237292d78aaa0c386c7b28b2
Author: Peter Zijlstra <peterz@infradead.org>
AuthorDate: Thu, 15 Dec 2011 11:47:00 -0800
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 16 Dec 2011 09:44:58 +0100
sched: Fix select_idle_sibling() regression in selecting an idle SMT sibling
Mike Galbraith reported that this recent commit:
commit 4dcfe1025b513c2c1da5bf5586adb0e80148f612
Author: Peter Zijlstra <peterz@infradead.org>
Date: Thu Nov 10 13:01:10 2011 +0100
sched: Avoid SMT siblings in select_idle_sibling() if possible
stopped selecting an idle SMT sibling when there are no idle
cores in a single socket system.
Intent of the select_idle_sibling() was to fallback to an idle
SMT sibling, if it fails to identify an idle core. But this
fallback was not happening on systems where all the scheduler
domains had `SD_SHARE_PKG_RESOURCES' flag set.
Fix it. Slightly bigger patch of cleaning all these goto's etc
is queued up for the next release.
Reported-by: Mike Galbraith <efault@gmx.de>
Reported-by: Alex Shi <alex.shi@intel.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Link: http://lkml.kernel.org/r/1323978421.1984.244.camel@sbsiddha-desk.sc.intel.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched_fair.c | 14 ++++++++------
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
index a78ed27..8a39fa3 100644
--- a/kernel/sched_fair.c
+++ b/kernel/sched_fair.c
@@ -2352,13 +2352,11 @@ again:
if (!smt && (sd->flags & SD_SHARE_CPUPOWER))
continue;
- if (!(sd->flags & SD_SHARE_PKG_RESOURCES)) {
- if (!smt) {
- smt = 1;
- goto again;
- }
+ if (smt && !(sd->flags & SD_SHARE_CPUPOWER))
+ break;
+
+ if (!(sd->flags & SD_SHARE_PKG_RESOURCES))
break;
- }
sg = sd->groups;
do {
@@ -2378,6 +2376,10 @@ next:
sg = sg->next;
} while (sg != sd->groups);
}
+ if (!smt) {
+ smt = 1;
+ goto again;
+ }
done:
rcu_read_unlock();
next prev parent reply other threads:[~2011-12-16 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 19:47 [patch] sched: fix " Suresh Siddha
2011-12-16 8:44 ` Ingo Molnar
2011-12-16 11:36 ` tip-bot for Peter Zijlstra [this message]
2011-12-21 12:33 ` [tip:sched/urgent] sched: Fix " alex shi
2011-12-21 12:52 ` Peter Zijlstra
2011-12-21 19:42 ` Suresh Siddha
2011-12-22 1:31 ` Alex,Shi
2011-12-22 2:03 ` Suresh Siddha
2011-12-22 2:16 ` Alex,Shi
2011-12-22 6:59 ` Alex,Shi
2011-12-23 18:43 ` Suresh Siddha
2011-12-24 7:04 ` Shi, Alex
2012-01-06 8:14 ` 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=tip-ab2789213d224202237292d78aaa0c386c7b28b2@git.kernel.org \
--to=peterz@infradead.org \
--cc=alex.shi@intel.com \
--cc=efault@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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