From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Gautham R Shenoy <ego@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Balbir Singh <balbir@in.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [RFC PATCH v2 0/2] sched: Nominate a power-efficient ILB
Date: Sun, 26 Apr 2009 22:26:42 +0530 [thread overview]
Message-ID: <20090426165642.GA6182@dirshya.in.ibm.com> (raw)
In-Reply-To: <1240362322.27006.8548.camel@localhost.localdomain>
* Suresh Siddha <suresh.b.siddha@intel.com> [2009-04-21 18:05:22]:
> On Mon, 2009-04-13 at 21:55 -0700, Gautham R Shenoy wrote:
> > Now, the other power-savings settings such as the sched_mc/smt_power_savings
> > and the power-aware IRQ balancer try to balance tasks/IRQs by taking
> > the system topology into consideration, with the intention of keeping
> > as many "power-domains" (cores/packages) in the low-power state.
> >
> > The current idle-load-balancer nomination does not necessarily align towards
> > this policy. For eg, we could be having tasks and interrupts largely running
> > on the first package with the intention of keeping the second package idle.
> > Hence, CPU 0 may be busy. The first_cpu in the nohz.cpu_mask happens to be CPU1,
> > which in-turn becomes nominated as the idle-load balancer. CPU1 being from
> > the 2nd package, would in turn prevent the 2nd package from going into a
> > deeper sleep state.
> >
> > Instead the role of the idle-load balancer could have been assumed by an
> > idle CPU from the first package, thereby helping the second package go
> > completely idle.
>
> Can we also do this by default? i.e., even when no power-savings policy
> is selected.
>
> I don't see anything wrong by enabling this logic for all the cases.
Hi Suresh,
Thanks for the review. The selection of the idle-load-balancer
depends on the sched domain level with SD_POWERSAVINGS_BALANCE flag
set that indicates the cpu-package boundary. Hence this scheme
depends on sched_mc_powersavings being non zero so that the sched
domains (cpu level) are build based on cpu-package information.
The logical-cpu to cpu-package grouping information is not readily
available (in the sched domain) when power-saving policies are off.
We may need to look at selection of idle-load-balancer for maximum
performance (bandwidth utilisation) when power save policies are off.
--Vaidy
prev parent reply other threads:[~2009-04-26 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 4:55 Gautham R Shenoy
2009-04-14 4:55 ` [RFC PATCH 2 1/2] sched: Nominate idle load balancer from a semi-idle package Gautham R Shenoy
2009-04-14 10:01 ` [tip:sched/core] " tip-bot for Gautham R Shenoy
2009-04-14 17:32 ` [RFC PATCH 2 1/2] " Randy Dunlap
2009-04-14 4:55 ` [RFC PATCH 2 2/2] sched: Nominate a power-efficient ilb in select_nohz_balancer() Gautham R Shenoy
2009-04-14 10:01 ` [tip:sched/core] " tip-bot for Gautham R Shenoy
2009-04-14 9:48 ` [RFC PATCH v2 0/2] sched: Nominate a power-efficient ILB Peter Zijlstra
2009-04-14 9:58 ` Gautham R Shenoy
2009-04-22 1:05 ` Suresh Siddha
2009-04-26 16:56 ` Vaidyanathan Srinivasan [this message]
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=20090426165642.GA6182@dirshya.in.ibm.com \
--to=svaidy@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=balbir@in.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=suresh.b.siddha@intel.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
Powered by JetHome