Linux ACPI
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Erik Slagter <erik@slagter.name>
Cc: Jindrich Makovicka <makovick@gmail.com>, linux-acpi@vger.kernel.org
Subject: Re: No c2-c7 states on core i7
Date: Wed, 25 Nov 2009 01:59:55 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911250154350.8459@localhost.localdomain> (raw)
In-Reply-To: <4B0BE5B8.7060402@slagter.name>

> Yesterday I raised the clock to 3.4 Ghz and I set all voltages to "normal" and
> it seems to run fine. I will have to check under really heavy load yet, I will
> do that tonight. My motherboard has an option "power line load calibration", I
> guess that has something to do with it :-)
> 
> Interesting: I pulled out a "modern" (but cheapo, no fans) pcie vga card and
> replaced it with a very old pci card (I guess from 1996) and that saves me 20
> watts! That's more power than I problably ever could save using C states!

Yep, beware graphics card power.

> BTW on my ancient athlon-mp board, I could enable c2/c3 (although not
> supported by the bios) and that would save about ~40 watts of power. But it
> looks I won't see such a difference on modern CPU's, maybe because of the
> dynamic frequency scaling and enhanced c1? Is there anyone who can give me an
> indication of what to expect in powersavings by c2-c7 on modern cpu's?

On the mobile parts they used to publish the power limits for C-states,
but I don't see these numbers in the core i7 datasheet...

However, many have done comparisons of what you might expect for
idle vs loaded power.  eg.
http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=3634&p=17

In general, I don't view it as a Linux bug that the MB's BIOS
disables c-states when it is over-clocked.  Indeed, it is
quite possibly a BIOS feature.

Len Brown, Intel Open Source Technology Center




      reply	other threads:[~2009-11-25  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 14:28 No c2-c7 states on core i7 Erik Slagter
2009-11-21 17:45 ` Erik Slagter
2009-11-22 11:46 ` c1/c1e/c3/c6/c7 on linux Erik Slagter
2009-11-23  3:05 ` No c2-c7 states on core i7 ykzhao
2009-11-23  8:52   ` Erik Slagter
2009-11-23 16:11     ` Len Brown
2009-11-23 19:23       ` Erik Slagter
2009-11-23 19:26       ` Erik Slagter
2009-11-24 13:34         ` Jindrich Makovicka
2009-11-24 13:55           ` Erik Slagter
2009-11-25  6:59             ` Len Brown [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=alpine.LFD.2.00.0911250154350.8459@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=erik@slagter.name \
    --cc=linux-acpi@vger.kernel.org \
    --cc=makovick@gmail.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