From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Prashanth Nageshappa <prashanth@linux.vnet.ibm.com>,
mingo@kernel.org, LKML <linux-kernel@vger.kernel.org>,
roland@kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sched: balance_cpu to consider other cpus in its group as target of (pinned) task migration
Date: Mon, 4 Jun 2012 18:37:41 +0530 [thread overview]
Message-ID: <20120604130740.GC25126@linux.vnet.ibm.com> (raw)
In-Reply-To: <1338814063.7356.192.camel@marge.simpson.net>
* Mike Galbraith <efault@gmx.de> [2012-06-04 14:47:43]:
> You need a good reason to run RT, and being able to starve others to
> death ain't it, so I don't see a good reason to care about the 95% case
> enough to fiddle with load balancing to accommodate the oddball case.
While starvation of SCHED_OTHER task was an extreme case, the point
remains that SCHED_OTHER tasks are better served by moving them away
from cpus running rt tasks that are partially cpu intensive. While the
current code has the nuts and bolts to recognize this situation
(scale_rt_power), it fails to effect SCHED_OTHER task movement because of how
one cpu from a sched_group is designated to pull tasks on behalf of its
siblings and that chosen balance_cpu may not be in the task's cpus_allowed mask
(but the task can run on one or more of its sibling cpus).
- vatsa
next prev parent reply other threads:[~2012-06-04 13:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 5:57 [PATCH] sched: balance_cpu to consider other cpus in its group as target of (pinned) task migration Prashanth Nageshappa
2012-06-04 9:00 ` Peter Zijlstra
2012-06-04 11:41 ` Srivatsa Vaddagiri
2012-06-04 11:49 ` Peter Zijlstra
2012-06-04 12:27 ` Srivatsa Vaddagiri
2012-06-04 11:51 ` Peter Zijlstra
2012-06-04 9:25 ` Mike Galbraith
2012-06-04 11:53 ` Peter Zijlstra
2012-06-04 12:47 ` Mike Galbraith
2012-06-04 13:07 ` Srivatsa Vaddagiri [this message]
2012-06-04 14:30 ` Mike Galbraith
2012-06-04 14:38 ` Srivatsa Vaddagiri
2012-06-04 14:41 ` Mike Galbraith
2012-06-04 15:00 ` Srivatsa Vaddagiri
2012-06-04 15:21 ` Peter Zijlstra
2012-06-04 15:25 ` Srivatsa Vaddagiri
2012-06-04 15:33 ` Peter Zijlstra
2012-06-04 15:46 ` Srivatsa Vaddagiri
2012-06-04 16:56 ` Mike Galbraith
2012-06-04 17:37 ` Srivatsa Vaddagiri
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=20120604130740.GC25126@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prashanth@linux.vnet.ibm.com \
--cc=roland@kernel.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