From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, a.p.zijlstra@chello.nl,
ego@in.ibm.com, tglx@linutronix.de, mingo@elte.hu,
andi@firstfloor.org, venkatesh.pallipadi@intel.com,
vatsa@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com
Subject: Re: [v2 PATCH 0/4] timers: framework for migration between CPU
Date: Fri, 6 Mar 2009 09:53:33 +0530 [thread overview]
Message-ID: <20090306042333.GA9190@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090305161451.0da40645@infradead.org>
* Arjan van de Ven <arjan@infradead.org> [2009-03-05 16:14:51]:
> On Wed, 4 Mar 2009 17:42:49 +0530
> Arun R Bharadwaj <arun@linux.vnet.ibm.com> wrote:
> > With the timers queued I measure the sleep state residency
> > for a period of 10s.
> > Next, I enable timer migration and measure the sleep state
> > residency period.
>
> is your table in seconds? Because realistically, at least on PC like
> hardware, doing work to get sleep times over a 100 / 200 msecs or so
> isn't going to save you any amount of measurable power anymore...
>
Hi Arjan,
Yes, the table is in seconds.
Rather than looking at timer migration as a direct means of obtaining
power savings, I would like to see it as one of the mechanisms which
would aid in preventing an almost idle cpu from waking up
unnecessarily, thereby causing power penalty. Otherwise, there is a
chance of all the CPUs in a particular package being idle and the
entire package going into deep sleep.
So we cannot really get big power savings just by doing timer
migration alone.
--arun
>
>
> --
> Arjan van de Ven Intel Open Source Technology Centre
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
prev parent reply other threads:[~2009-03-06 4:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 12:12 [v2 PATCH 0/4] timers: framework for migration between CPU Arun R Bharadwaj
2009-03-04 12:14 ` [v2 PATCH 1/4] timers: framework to identify pinned timers Arun R Bharadwaj
2009-03-05 16:53 ` Oleg Nesterov
2009-03-06 6:14 ` Arun R Bharadwaj
2009-03-06 15:03 ` Oleg Nesterov
2009-03-06 7:01 ` Arun R Bharadwaj
2009-03-04 12:16 ` [v2 PATCH 2/4] timers: identifying the existing pinned hrtimers Arun R Bharadwaj
2009-03-04 12:18 ` [v2 PATCH 3/4] timers: sysfs hook to enable timer migration Arun R Bharadwaj
2009-03-04 12:19 ` [v2 PATCH 4/4] timers: logic " Arun R Bharadwaj
2009-03-04 16:33 ` Daniel Walker
2009-03-04 16:52 ` Arun R Bharadwaj
2009-03-05 15:34 ` Oleg Nesterov
2009-03-05 16:23 ` Oleg Nesterov
2009-03-06 3:21 ` Gautham R Shenoy
2009-03-06 14:50 ` Oleg Nesterov
2009-03-06 15:49 ` Gautham R Shenoy
2009-03-06 17:08 ` Oleg Nesterov
2009-03-06 17:26 ` Gautham R Shenoy
2009-03-04 17:33 ` [v2 PATCH 0/4] timers: framework for migration between CPU Ingo Molnar
2009-03-04 18:06 ` Vaidyanathan Srinivasan
2009-03-04 18:29 ` Ingo Molnar
2009-03-06 0:14 ` Arjan van de Ven
2009-03-06 4:23 ` Arun R Bharadwaj [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=20090306042333.GA9190@linux.vnet.ibm.com \
--to=arun@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vatsa@linux.vnet.ibm.com \
--cc=venkatesh.pallipadi@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