From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
dietmar.eggemann@arm.com, preeti@linux.vnet.ibm.com,
tony.luck@intel.com, fenghua.yu@intel.com,
schwidefsky@de.ibm.com, james.hogan@imgtec.com,
cmetcalf@tilera.com, benh@kernel.crashing.org,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v2 5/7] sched: add a new SD_SHARE_POWERDOMAIN for sched_domain
Date: Wed, 19 Mar 2014 13:01:22 +0100 [thread overview]
Message-ID: <20140319120122.GK27632@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <1395165409-18055-6-git-send-email-vincent.guittot@linaro.org>
On Tue, Mar 18, 2014 at 06:56:47PM +0100, Vincent Guittot wrote:
> A new flag SD_SHARE_POWERDOMAIN is created to reflect whether groups of CPUs
> in a sched_domain level can or not reach different power state. As an example,
> the flag should be cleared at CPU level if groups of cores can be power gated
> independently. This information can be used to add load balancing level between
> group of CPUs than can power gate independantly. The default behavior of the
> scheduler is to spread tasks across CPUs and groups of CPUs
> so the flag is set into all sched_domains.
I suppose that is the part Preeti stumbled over; as did I. Its not set
at all.
next prev parent reply other threads:[~2014-03-19 12:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 17:56 [PATCH v2 0/7] rework sched_domain topology description Vincent Guittot
2014-03-18 17:56 ` [PATCH v2 1/7] sched: remove unused SCHED_INIT_NODE Vincent Guittot
2014-03-19 11:07 ` James Hogan
2014-03-18 17:56 ` [PATCH v2 2/7] sched: rework of sched_domain topology definition Vincent Guittot
2014-03-19 6:01 ` Preeti U Murthy
2014-03-19 11:27 ` Dietmar Eggemann
2014-03-19 12:41 ` Peter Zijlstra
2014-03-19 13:33 ` Vincent Guittot
2014-03-19 15:22 ` Dietmar Eggemann
2014-03-19 16:14 ` Vincent Guittot
2014-03-19 13:46 ` Dietmar Eggemann
2014-03-18 17:56 ` [PATCH v2 3/7] sched: s390: create a dedicated topology table Vincent Guittot
2014-03-18 17:56 ` [PATCH v2 4/7] sched: powerpc: " Vincent Guittot
2014-03-19 6:04 ` Preeti U Murthy
2014-03-18 17:56 ` [PATCH v2 5/7] sched: add a new SD_SHARE_POWERDOMAIN for sched_domain Vincent Guittot
2014-03-19 6:21 ` Preeti U Murthy
2014-03-19 9:52 ` Vincent Guittot
2014-03-19 11:05 ` Preeti U Murthy
2014-03-19 12:26 ` Vincent Guittot
2014-03-19 11:59 ` Peter Zijlstra
2014-03-19 12:28 ` Vincent Guittot
2014-03-19 12:01 ` Peter Zijlstra [this message]
2014-03-19 12:29 ` Vincent Guittot
2014-03-18 17:56 ` [PATCH v2 6/7] sched: ARM: create a dedicated scheduler topology table Vincent Guittot
2014-03-18 17:56 ` [PATCH v2 7/7] sched: powerpc: Add SD_SHARE_POWERDOMAIN for SMT level Vincent Guittot
2014-03-19 12:05 ` Peter Zijlstra
2014-03-19 12:30 ` Vincent Guittot
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=20140319120122.GK27632@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=dietmar.eggemann@arm.com \
--cc=fenghua.yu@intel.com \
--cc=james.hogan@imgtec.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
--cc=vincent.guittot@linaro.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
Powered by JetHome