public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: x86_64 and AMD with C1E
Date: Mon, 1 Oct 2007 15:09:53 +0200	[thread overview]
Message-ID: <20071001130953.GC17357@one.firstfloor.org> (raw)
In-Reply-To: <b70f2f960710010546k4658aa1ay466f243ac707c989@mail.gmail.com>

> No, it boot and work normally. The only thing i bother, is the additional

Ok you want an additional feature; not a bug fixed.

Please make that always clear.

> 260 timer interrupts per seconds.
> Here is short result:
> 
> c1e enabled:
>   -- power consumption about 23 watts
>   -- there is only C1 power state enabled
>   -- there are about 260 timer interrupts per seconds

If you want less timer interrupts in a standard kernel
a simple way is to compile with CONFIG_HZ=100

> tested with x86_64(2.6.22, 2.6.23-rc8, 2.6.23-rc8-hrt1), i386(2.6.21, 2.6.22,
> 2.6.23-rc5-hrt1)

There is normally a threshold above which you don't save significantly
more power by doing less timer interrupts. You can test this 
by doing the CONFIG_HZ=100 above.

Also as a warning: most simple methods of measuring power (like
watching battery consumption) are fairly imprecise and can
have large systematic errors.

Normally reducing the timer interrupts significantly only helps
on longer latency sleep modi; which is C2+ where the latency
of going in/out of the sleep is reaching towards half of 
the timer period. But that is not the case on the AMD C1e
implementations as far as I know -- they're fairly fast.

> c1e disabled:
>   -- power consumption about 27 watts

Don't do this then.

> I want to reduce the power consumption of my notebook. I see the 2
> possibility:
>   -- remove 260 additional timer interrupts (c1e enabled case )

It's unclear it will really help all that much. Most likely
you'll get more bang for the buck by disabling other devices.
e.g. reducing the backlight or unloading USB/firewire/sound
can do wonders.

>   -- force enable C1, C2 and C3 states  (c1e disabled case)

If the BIOS doesn't announce it the platform doesn't implement it.

-Andi

  parent reply	other threads:[~2007-10-01 13:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  6:15 x86_64 and AMD with C1E Mikhail Kshevetskiy
2007-10-01  9:33 ` Andi Kleen
     [not found]   ` <b70f2f960710010546k4658aa1ay466f243ac707c989@mail.gmail.com>
2007-10-01 12:50     ` Fwd: " Mikhail Kshevetskiy
2007-10-01 14:14       ` Thomas Gleixner
2007-10-01 14:32         ` Andi Kleen
2007-10-01 14:59           ` Thomas Gleixner
2007-10-01 15:21             ` Andi Kleen
2007-10-01 16:44               ` Thomas Gleixner
2007-10-01 17:56               ` Chuck Ebbert
2007-10-01 14:33         ` Mikhail Kshevetskiy
2007-10-01 13:09     ` Andi Kleen [this message]
2007-10-01 14:06       ` Arjan van de Ven
2007-10-01 14:40       ` Mikhail Kshevetskiy
2007-10-19 16:39 ` Chuck Ebbert
2007-10-24 21:26   ` Mikhail Kshevetskiy
2007-10-24 21:41     ` Chuck Ebbert
2007-10-24 22:12       ` Thomas Gleixner
2007-10-24 22:42       ` Mikhail Kshevetskiy
2007-12-15 11:06       ` Thomas Gleixner

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=20071001130953.GC17357@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.kshevetskiy@gmail.com \
    --cc=tglx@linutronix.de \
    /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