public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: [announce] Intel announces the PowerTOP utility for Linux
Date: Fri, 11 May 2007 16:07:18 -0700	[thread overview]
Message-ID: <4644F726.1050806@linux.intel.com> (raw)


What's eating the battery life of my laptop? Why isn't it many more 
hours? Which software component causes the most power to be burned? 
These are important questions without a good answer... until now.

The Linux 2.6.21 kernel introduces the so called tickless-idle 
feature. This feature allows the processor to be really idle for long 
periods of time, rather than having to wake up every millisecond for 
the timer tick. Current processors save a lot of power if they are 
idle for long periods, which translates into a longer battery life for 
your laptop, or a lower energy bill for your datacenter. However, a 
Linux system consists of more software than just the kernel, and there 
are many tunables involved. It's not easy to see what is going on, and 
as a result the behavior is sometimes far from optimal, and a lot of 
power is wasted.

Intel is proud to announce the PowerTOP tool 
(http://www.linuxpowertop.org), a program that collects the various 
pieces of information from your system and presents an overview of how 
well your laptop is doing in terms of power savings. In addition, 
PowerTOP will provide an indication of which tunables and software 
components are the biggest offenders in slurping up your battery time. 
PowerTOP will update it's display frequently so that you can directly 
see the impact of any changes you are making.

A typical Linux distribution has many components that wake the 
processor up frequently for no good reason. In our testing with 
PowerTOP, we have seen many cases where with some simple fixes, the 
battery life of typical laptops was increased by one hour or more!

We are providing fixes for several of the issues we identified, and we 
encourage the Linux community to help us in this quest to get the 
maximum battery life out of your (hopefully Intel based) laptops. Try 
the PowerTOP tool, join the mailing list or the IRC channel and 
provide feedback, problem reports or fixes!

Website:      http://www.linuxpowertop.org
IRC:          irc.oftc.net    #powertop channel
Mailing list: http://www.bughost.org/mailman/listinfo/power

             reply	other threads:[~2007-05-11 23:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 23:07 Arjan van de Ven [this message]
2007-05-12  0:17 ` [announce] Intel announces the PowerTOP utility for Linux Matt Mackall
2007-05-12  1:40   ` Jose Celestino
2007-05-12  2:39     ` Matt Mackall
2007-05-12  4:09       ` Jose Celestino
2007-05-12 11:00 ` Jan Engelhardt
2007-05-12 17:44   ` Arjan van de Ven
2007-05-12 21:12 ` Alistair John Strachan
2007-05-14 20:22   ` Jan Engelhardt
2007-05-14 20:42     ` Alistair John Strachan
     [not found] <fa.FTEkheuP0nHOUv0cCp0k8pBuoMU@ifi.uio.no>
2007-05-15  0:13 ` Robert Hancock
2007-05-15 16:30   ` Ondrej Zary
2007-05-16  7:52     ` Schmidt Michal
2007-05-16 14:20       ` 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=4644F726.1050806@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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