From: "Alex,Shi" <alex.shi@intel.com>
To: Norbert Preining <preining@logic.at>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Chen, Tim C" <tim.c.chen@intel.com>,
"arjan@infradead.org" <arjan@infradead.org>,
"efault@gmx.de" <efault@gmx.de>,
"Li, Shaohua" <shaohua.li@intel.com>, tglx <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: high power consumption in recent kernels
Date: Fri, 17 Sep 2010 10:09:34 +0800 [thread overview]
Message-ID: <1284689374.17745.89.camel@debian> (raw)
In-Reply-To: <1284355277.26157.8109.camel@debian>
> > - how to reduce the "extra timer interrupt"?
> The timer was listed in /proc/timer_stats, you can post its contents,
> and let's see what is abnormal here.
>
Norbert, did you try the patch?
We are still thinking the too many "extra timer interrupts" on your
system, maybe the following message can give some help. So, could you
like to check if your system is using pit timer?
#cat /proc/timer_list
Or some APP/system services in your system is using lots of timer?
===
http://www.linuxpowertop.org/faq.php
Even with a tickless kernel, there are some timer ticks still happening:
1.) For userspace events (also shown in the lower "top 10 events" list).
2.) The kernel still has timer ticks when userspace is executing code,
to sample and get data for the "top" program.
3.) Hardware timers have a maximum time they can be set for, for the PIT
timer (the one used if you don't have HPET active). This is around 27
milliseconds. If you would have longer sleep times than the maximum, the
kernel has no choice but to set the timer to the maximum repeatedly
until the actual event is approaching.
The "extra timer interrupts" data is a combination fo 1 and 3.
next prev parent reply other threads:[~2010-09-17 2:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1283840425.26157.6486.camel@debian>
[not found] ` <20100909093140.GC29648@gamma.logic.tuwien.ac.at>
[not found] ` <EA929A9653AAE14F841771FB1DE5A1366008738EC2@rrsmsx501.amr.corp.intel.com>
[not found] ` <20100909205115.GD11053@gamma.logic.tuwien.ac.at>
[not found] ` <1284107099.402.30.camel@laptop>
2010-09-10 14:48 ` high power consumption in recent kernels Shi, Alex
2010-09-10 14:54 ` Norbert Preining
2010-09-13 5:21 ` Alex,Shi
2010-09-17 2:09 ` Alex,Shi [this message]
2010-09-22 15:44 ` Norbert Preining
2010-09-28 10:40 ` Alex,Shi
2010-09-29 14:39 ` Norbert Preining
2010-09-29 15:48 ` Chen, Tim C
2010-09-30 0:50 ` Alex,Shi
2010-09-30 2:01 ` Norbert Preining
2010-09-30 6:59 ` Norbert Preining
2010-09-30 8:27 ` Alex,Shi
2010-09-30 12:36 ` Peter Zijlstra
2010-09-30 13:21 ` Shi, Alex
2010-07-06 16:45 Norbert Preining
2010-07-08 9:06 ` Peter Zijlstra
2010-07-08 11:57 ` Arjan van de Ven
2010-07-08 11:58 ` Peter Zijlstra
2010-07-08 12:04 ` Norbert Preining
2010-07-08 12:22 ` Peter Zijlstra
2010-07-08 12:46 ` Norbert Preining
2010-07-08 13:23 ` Peter Zijlstra
2010-07-08 15:59 ` Peter Zijlstra
2010-07-08 19:06 ` Peter Zijlstra
2010-07-08 19:40 ` Mike Galbraith
2010-07-08 20:44 ` Peter Zijlstra
2010-07-09 3:08 ` Arjan van de Ven
2010-07-09 5:55 ` Mike Galbraith
2010-07-08 19:37 ` Mike Galbraith
2010-07-08 15:11 ` Arjan van de Ven
2010-07-09 19:09 ` Pavel Machek
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=1284689374.17745.89.camel@debian \
--to=alex.shi@intel.com \
--cc=arjan@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=preining@logic.at \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@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