public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Norbert Preining <preining@logic.at>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	akpm <akpm@linux-foundation.org>
Subject: Re: high power consumption in recent kernels
Date: Thu, 08 Jul 2010 13:58:23 +0200	[thread overview]
Message-ID: <1278590303.1900.91.camel@laptop> (raw)
In-Reply-To: <20100708045711.398d4e26@infradead.org>

On Thu, 2010-07-08 at 04:57 -0700, Arjan van de Ven wrote:
> On Thu, 08 Jul 2010 11:06:32 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
> 
> > On Wed, 2010-07-07 at 01:45 +0900, Norbert Preining wrote:
> > 
> > > it seems that some of the (?)recent(?) changes have increased the
> > > power consumption of my note book considerably.
> > > 
> > > First of all, running powertop with normal programs started, but 
> > > doing nothing, I am still at 14W while I could go down to 9W before
> > > (but the 9W was with dimmed display).
> > > 
> > > In the list of top causes for wakeup I have
> > > Top causes for wakeups:
> > >   34.2% (185.3)   [kernel scheduler] Load balancing tick
> > >   23.9% (129.6)   [extra timer interrupt]
> > >   10.8% ( 58.6)   firefox-bin
> > >    9.2% ( 49.7)   [iwlagn] <interrupt>
> > >    7.2% ( 39.1)   [kernel core] hrtimer_start (tick_sched_timer)
> > >    3.9% ( 20.9)   PS/2 keyboard/mouse/touchpad interrupt
> > > which show one new thing to me I haven't seen before, the Loa
> > > balancing tick.
> > 
> > I think that is what powertop calls our regular tick (Arjan?), and as
> 
> it's "hrtimer_start_range_ns (tick_sched_timer)" if it's done by the
> idle thread.
> 

then wth is "[kernel scheduler] load balancing tick"?
and for that matter, what is "[extra timer interrupt]", surely the timer
hardware doesn't generate spurious interrupts?

  reply	other threads:[~2010-07-08 11:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 16:45 high power consumption in recent kernels 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 [this message]
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
     [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         ` Shi, Alex
2010-09-10 14:54           ` Norbert Preining
2010-09-13  5:21             ` Alex,Shi
2010-09-17  2:09               ` Alex,Shi
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

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=1278590303.1900.91.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=preining@logic.at \
    /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