From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jonathan@jonmasters.org
Cc: Lee Revell <rlrevell@joe-job.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robert Love <rml@novell.com>
Subject: Re: How is user space notified of CPU speed changes?
Date: Sun, 24 Oct 2004 15:04:18 +0100 [thread overview]
Message-ID: <1098626656.24108.12.camel@localhost.localdomain> (raw)
In-Reply-To: <35fb2e590410231635616f10c9@mail.gmail.com>
On Sul, 2004-10-24 at 00:35, Jon Masters wrote:
> Out of sheer interest, you said you had an example box which did this.
> I've never actually seen a modern SMP setup with different cock
> frequencies (even accepting it's possible) - can you give me a more
> modern example? I'm sure they're out there, I've just missed it, and I
> have to confess to not being aware that Linux supported this kind of
> setup.
The classic setups were dual PIII type systems - common FSB clock but
different multipliers for the processors. A lot of dual slot 1 boards
ended up with weird processor combinations.
Modern systems that don't tie the tsc include the big IBM 440 series
systems.
Alan
next prev parent reply other threads:[~2004-10-24 15:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 23:01 How is user space notified of CPU speed changes? Lee Revell
2004-10-22 11:23 ` Alan Cox
2004-10-22 14:12 ` Con Kolivas
2004-10-22 18:05 ` Lee Revell
2004-10-22 18:57 ` Andreas Dilger
2004-10-22 19:40 ` Chris Friesen
2004-10-22 19:46 ` Lee Revell
2004-10-22 20:28 ` Alan Cox
2004-10-22 21:46 ` Chris Friesen
2004-10-22 23:25 ` Lee Revell
2004-10-25 15:28 ` Chris Friesen
2004-10-23 5:10 ` Lee Revell
2004-10-23 10:53 ` Matthew Garrett
2004-10-23 21:19 ` Alan Cox
2004-10-23 22:42 ` Lee Revell
2004-10-23 23:17 ` Jon Masters
2004-10-24 1:40 ` Lee Revell
2004-10-24 14:02 ` Alan Cox
2004-10-26 2:38 ` Lee Revell
2004-10-26 4:05 ` Lee Revell
2004-10-23 23:35 ` Jon Masters
2004-10-23 23:36 ` Jon Masters
2004-10-24 14:04 ` Alan Cox [this message]
2004-10-25 5:53 ` Joel Becker
2004-10-24 20:02 ` Robert Love
[not found] <1098399709.4131.23.camel@krustophenia.net.suse.lists.linux.kernel>
[not found] ` <1098444170.19459.7.camel@localhost.localdomain.suse.lists.linux.kernel>
[not found] ` <1098508238.13176.17.camel@krustophenia.net.suse.lists.linux.kernel>
[not found] ` <1098566366.24804.8.camel@localhost.localdomain.suse.lists.linux.kernel>
2004-10-23 23:54 ` Andi Kleen
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=1098626656.24108.12.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=rml@novell.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.