public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Chris <chris@directcommunications.net>, linux-kernel@vger.kernel.org
Subject: Re: It hurts when I shoot myself in the foot
Date: Thu, 23 May 2002 10:33:05 -0700	[thread overview]
Message-ID: <20020523173305.GC4006@matchmail.com> (raw)
In-Reply-To: <200205221615.g4MGFCH30271@directcommunications.net> <acha7p$cge$1@cesium.transmeta.com> <20020523034821.GK458@turbolinux.com> <20020523044933.GB4006@matchmail.com> <20020523054219.GL458@turbolinux.com>

On Wed, May 22, 2002 at 11:42:19PM -0600, Andreas Dilger wrote:
> On May 22, 2002  21:49 -0700, Mike Fedyk wrote:
> > On Wed, May 22, 2002 at 09:48:21PM -0600, Andreas Dilger wrote:
> > > There was a kernel patch posted about 5 or so months ago which would
> > > "handle" this setup (CPUs with the same clock speed, but different
> > > multipliers).  Alan Cox said it probably was a bad idea, so it wouldn't
> > > go into the kernel, but the patch may still be usable.
> > > 
> > > This is sometimes called "asymmetric multiprocessing", and the thread
> > > is at http://marc.theaimsgroup.com/?l=linux-kernel&m=98519070331478&w=4
> > 
> > I thought asymmetric multiprocessing would support CPUs with different
> > speeds.  ie, 400 & 450mhz.  How would you get different multipliers and same
> > Mhz when the CPUs are on the same FSB(ignoring AMD SMP where each processor
> > has an exclusive FSB, and this might be possible)?
> 
> That was what I was trying to say: same FSB speed * different multipliers
> = different CPU MHZ, like what the original poster is asking about.
> I don't think it is possible to configure a motherboard to have different
> FSB speeds for two processors.
>

Me neither, but it seems theoretically possible.

> > There was a patch to compare the different features on the CPUs available
> > and use the subset available on all processors.
> 
> Hmm, maybe if you had actually read my email 

I did. ;)

> and followed the URL I posted, 

That I didn't do. :(

>you would have found the patch to which you refer ;-).

And you are correct.  That is the exact patch to which I was referring.

Mike

  reply	other threads:[~2002-05-23 17:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22 16:15 It hurts when I shoot myself in the foot Chris
2002-05-22 23:39 ` H. Peter Anvin
2002-05-23  3:48   ` Andreas Dilger
2002-05-23  4:49     ` Mike Fedyk
2002-05-23  5:42       ` Andreas Dilger
2002-05-23 17:33         ` Mike Fedyk [this message]
2002-05-23 22:28           ` Vojtech Pavlik
2002-05-24  7:32             ` Mike Fedyk
2002-05-24  7:36               ` Vojtech Pavlik
2002-05-24 15:28         ` Alan Cox
2002-05-24 15:20           ` Kasper Dupont
2002-05-24 15:50             ` Alan Cox
2002-05-24 15:36               ` Kasper Dupont
2002-05-24 16:09                 ` Alan Cox
2002-05-24 16:39                   ` Kasper Dupont
2002-05-24 18:44                     ` Alan Cox
2002-05-24 16:36                 ` Austin Gonyou

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=20020523173305.GC4006@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=chris@directcommunications.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox