From: Dave Jones <davej@redhat.com>
To: M C <kingming0811@yahoo.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: about cpufreq on intel dual core processor
Date: Wed, 22 Aug 2007 20:18:15 -0400 [thread overview]
Message-ID: <20070823001815.GD18739@redhat.com> (raw)
In-Reply-To: <193428.18959.qm@web39710.mail.mud.yahoo.com>
On Sat, Aug 18, 2007 at 07:54:01AM -0700, M C wrote:
> Hi, I have a simple question about cpufreq on intel dualcore processor.
>
> if each core has six frequency levels, then should i change the frequency levels for both of the cores simultaneously or i can change them separately?
>
> because the processor supports hyper threading techonogy, so there are fours cores in the linux system. then how should i treat the four cpu when i want to do the frequency scaling?
You are able to set different frequencies per core, however you only
save power per-socket, so unless they're all ramped down, you won't
be lowering the voltage of the socket if one core keeps the package busy.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-08-23 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 14:54 about cpufreq on intel dual core processor M C
2007-08-23 0:18 ` Dave Jones [this message]
2007-08-23 4:48 ` Arjan van de Ven
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=20070823001815.GD18739@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=kingming0811@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.