From: Dominik Brodowski <linux@brodo.de>
To: John Clemens <john@deater.net>
Cc: cpufreq@www.linux.org.uk
Subject: Re: SMP status?
Date: Tue, 22 Jul 2003 14:04:22 +0200 [thread overview]
Message-ID: <20030722120422.GC1160@brodo.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0307210100390.18644-100000@pianoman.cluster.toy>
On Mon, Jul 21, 2003 at 01:06:05AM -0400, John Clemens wrote:
>
> Out of curiousity, has anyone thought about what it would take get SMP
> support into cpufreq? I'm thinking about servers...
It's already done. The generic cpufreq core is perfectly SMP-capable, the
x86 timing updates [in arch/i386/kernel/timers/timer_tsc.c] is
SMP-capable, the /proc/sys/, /proc and /sys/devices interfaces are
SMP-capable. However, it's more a question of which CPUs support frequency
and voltage scaling. There's no "speedstep" for server-grade processors yet,
though AMD is reportedly thinking of including PowerNow in future releases
of their AMD64 processors. So, on x86 only the throttling-driver
"p4-clockmod" does provide SMP [and Hyperthreading!] support.
On other architectures cpufreq + SMP is more widely available, e.g. on
sparc64.
> how big of a rats nest is this, as bad as i think it is?
It seems to work :-)
Dominik
prev parent reply other threads:[~2003-07-22 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 5:06 SMP status? John Clemens
2003-07-22 12:04 ` Dominik Brodowski [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=20030722120422.GC1160@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=john@deater.net \
/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