From: Wes Felter <wesley@felter.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual Core on Linux questions
Date: Mon, 20 Mar 2006 13:23:32 -0600 [thread overview]
Message-ID: <dvmvge$v43$1@sea.gmane.org> (raw)
In-Reply-To: <20060318082434.M33432@linuxwireless.org>
Alejandro Bonilla wrote:
> Hi,
>
> I have a few questions about the PM Dual Core and how could it really work
> with Linux. Sorry if there are new patches on LKML about any of these things:
>
> Could each processor or die, have it's own cpufreq scaling governor?
>
> Is there a way to allow one die to be idle and let the other one normal?
>
> So in other words, could we manage these processors speedstep, utilization and
> workload individually?
This depends on your hardware. I was reading the Sossaman data sheet the
other day, and it says that the entire chip must run at the same
frequency. You can set each core to a different frequency, but the
hardware chooses the higher of the two. Likewise, the entire chip can
sleep, but individual cores can only go into C1. I imagine the Core Duo
is the same.
IIRC, the dual-core Opterons behave a little differently but the two
cores still have to run at the same frequency.
Wes Felter - wesley@felter.org
next prev parent reply other threads:[~2006-03-20 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 8:35 Dual Core on Linux questions Alejandro Bonilla
2006-03-18 8:58 ` Jeff Garzik
2006-03-18 9:03 ` Alejandro Bonilla
2006-03-18 10:49 ` Mattia Dongili
2006-03-18 9:21 ` Arjan van de Ven
2006-03-20 19:23 ` Wes Felter [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 3:36 Pallipadi, Venkatesh
2006-03-23 3:44 ` Jeff Garzik
2006-03-29 19:51 ` Bill Davidsen
2006-03-30 20:31 ` Jeff Garzik
2006-04-04 19:30 ` Bill Davidsen
2006-03-23 17:55 ` Mattia Dongili
2006-03-23 3:51 Pallipadi, Venkatesh
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='dvmvge$v43$1@sea.gmane.org' \
--to=wesley@felter.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 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.