Re: It hurts when I shoot myself in the foot
Mike Fedyk (mfedyk@matchmail.com)
Fri, 24 May 2002 00:32:16 -0700
On Fri, May 24, 2002 at 12:28:29AM +0200, Vojtech Pavlik wrote:
> On Thu, May 23, 2002 at 10:33:05AM -0700, Mike Fedyk wrote:
> > 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.
>
> It is not, they are both on the same FSB, at least in Pentium II/III case.
And if you read even what is quoted above in this message you would notice
that we are not talking about Intel SMP, but AMD SMP, or more correctly, AMD
SMP licensed from Alpha. What you say is true for Intel SMP though.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/