From: Nikhil Rao <ncrao@google.com>
To: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>
Cc: Venkatesh Pallipadi <venki@google.com>,
linux-kernel@vger.kernel.org, Nikhil Rao <ncrao@google.com>
Subject: [PATCH 2/3] sched: drop group_capacity to 1 only if remote group has no running tasks
Date: Mon, 27 Sep 2010 17:29:57 -0700 [thread overview]
Message-ID: <1285633798-26886-3-git-send-email-ncrao@google.com> (raw)
In-Reply-To: <1285633798-26886-1-git-send-email-ncrao@google.com>
When SD_PREFER_SIBLING is set on a sched domain, drop group_capacity to 1
only if the remote sched group has no running tasks. This addresses the case
where you have two tasks on one socket and the other socket is idle, in which
case you drop the capacity to 1. If the remote group has >=1 running task, then
there is no difference from a cache-sharing perspective.
Signed-off-by: Nikhil Rao <ncrao@google.com>
---
kernel/sched_fair.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
index de8a6a0..33a7985 100644
--- a/kernel/sched_fair.c
+++ b/kernel/sched_fair.c
@@ -2548,7 +2548,7 @@ static inline void update_sd_lb_stats(struct sched_domain *sd, int this_cpu,
* first, lower the sg capacity to one so that we'll try
* and move all the excess tasks away.
*/
- if (prefer_sibling)
+ if (prefer_sibling && !sgs.sum_nr_running)
sgs.group_capacity = min(sgs.group_capacity, 1UL);
if (local_group) {
--
1.7.1
next prev parent reply other threads:[~2010-09-28 0:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 0:29 [PATCH 0/3][RFC] Improve load balancing when tasks have large weight differential Nikhil Rao
2010-09-28 0:29 ` [PATCH 1/3] sched: set group_imb only a task can be pulled from the busiest cpu Nikhil Rao
2010-09-28 0:29 ` Nikhil Rao [this message]
2010-09-28 23:04 ` [PATCH 2/3] sched: drop group_capacity to 1 only if remote group has no running tasks Suresh Siddha
2010-10-11 21:20 ` Nikhil Rao
2010-09-28 0:29 ` [PATCH 3/3] sched: do not consider SCHED_IDLE tasks to be cache hot Nikhil Rao
2010-09-28 13:57 ` [PATCH 0/3][RFC] Improve load balancing when tasks have large weight differential Mike Galbraith
2010-09-28 21:15 ` Nikhil Rao
2010-09-29 1:45 ` Mike Galbraith
2010-09-29 19:32 ` Nikhil Rao
2010-10-04 3:08 ` Mike Galbraith
2010-10-06 8:23 ` Nikhil Rao
2010-10-08 7:22 ` Mike Galbraith
2010-10-08 20:34 ` Nikhil Rao
2010-10-10 10:15 ` Mike Galbraith
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=1285633798-26886-3-git-send-email-ncrao@google.com \
--to=ncrao@google.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=venki@google.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.