From: Len Brown <len.brown@intel.com>
To: Bjoern Schmidt <lucky21@uni-paderborn.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fsb of older cpu
Date: 09 Mar 2004 01:58:43 -0500 [thread overview]
Message-ID: <1078815523.2342.535.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F47CB@hdsmsx402.hd.intel.com>
C-states should be called Idle-states -- they're entered when the
processor is idle. No instructions are executed when in a C-state > 0.
C1 is supported by all processors automatically with some carefully
placed insructions inside the idle loop. Not all processors suport
higher C-states with more power savings in idle. You'll be able to tell
what is supported and what is used by looking in /proc/acpi/CPU0/power.
I'm not sure we update the counter to reflect entering C1...
Then there are P-states -- performance states. These are used by the
various cpufreq drivers such as speed-step(tm;-). These can modulate
both voltage and Mhz at the same time depending on load and are thus the
most effective and most desireable way to save cpu power w/ minimal
performance impact.
Thermal throttling is something else. This is invoked as the
passive-colling method of last resort when the processor is very hot
(busy). The actual clock to the processor is modulated so that it slows
down and thus power is saved in proportion to how much it is slowed
down. Throttling will noticeably slow down your system when you want it
fast the most -- heavy load.
Of course, then there is active cooling -- fan control...
cheers,
-Len
On Mon, 2004-03-08 at 16:53, Bjoern Schmidt wrote:
> Stefan Smietanowski schrieb:
> > I'm no expert on the subject but as I recall the processor sets the
> > internal clock (derived from fsb+multiplier) on startup so no matter
> > what you do do the running cpu it won't change it.
>
> I think there must be a way. In the BIOS there ist an option "half
> processor
> clock it is in idle". One time i have seen in /proc/cpuinfo" that the
> clock
> was at ~118MHz, but that is 6 Month ago and i have this never seen
> again...
> The problem is that with activated acpi the passive cooling does not
> seem to
> work although the cpu is very often in C2 and throttling mode is at 8.
> C1 is
> called extrem rarely (~1000 times per day), even if the system is
> under heavy
> load for a long time. I believe that C2 is not really supported by the
> cpu.
>
> --
> Greetings
> Bjoern Schmidt
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next parent reply other threads:[~2004-03-09 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F47CB@hdsmsx402.hd.intel.com>
2004-03-09 6:58 ` Len Brown [this message]
2004-03-09 11:16 ` fsb of older cpu Bjoern Schmidt
2004-03-09 11:35 ` Stefan Smietanowski
2004-03-09 12:07 ` Bjoern Schmidt
2004-03-10 4:17 ` Len Brown
2004-03-11 13:53 ` [BUG] " Bjoern Schmidt
2004-03-14 15:11 ` Bjoern Schmidt
2004-03-08 10:38 Bjoern Schmidt
2004-03-08 16:14 ` Bernd Schubert
2004-03-08 20:17 ` Bjoern Schmidt
2004-03-08 20:46 ` Zwane Mwaikambo
2004-03-08 21:14 ` Stefan Smietanowski
2004-03-08 23:06 ` Zwane Mwaikambo
2004-03-08 21:09 ` Stefan Smietanowski
2004-03-08 21:53 ` Bjoern Schmidt
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=1078815523.2342.535.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucky21@uni-paderborn.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