public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Orr <markorr@intersurf.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AMD SMP capability sanity checking.
Date: Fri, 16 Nov 2001 22:59:24 -0600	[thread overview]
Message-ID: <20011116225924.3390dc77.markorr@intersurf.com> (raw)
In-Reply-To: <20011116231141.A3030@faceprint.com>
In-Reply-To: <3BF5952E.E73BB648@resilience.com> <Pine.LNX.4.30.0111162353140.32578-100000@Appserv.suse.de> <20011116231141.A3030@faceprint.com>

On Fri, 16 Nov 2001 23:11:41 -0500
faceprint@faceprint.com (Nathan Walp) wrote:

> Actually, it's probably closer to:
> 
>    make cpu
>       |
>    smp tests run ok? -------> No, sell as XP
>       |
>    yes, do we have more demand
>    for XPs than we have supply
>    of those that didn't pass? -------> Yes, sell as XP
>       |
>    No, sell as MP

Yes, this is much closer to what's happening.  I'd bet that most
Palomino chips would pass the smp tests,  meaning many more MPs than
they'd ever need.    They're probably just putting a bucket in the
manufacturing stream,   testing those, and putting the rejects back
in the stream.

> Remember, AMD is just trying to make a buck.  If they've got a bunch of
> MP CPUs "sitting on the shelves" while no one can get their hands on the
> XPs, some of those MPs are going to "become" XPs.  For those of us on a
> budget, we can only hope to get one of *those* variety of XPs.

Umm...I cant see chips that have already been marked as MPs being
converted to XPs.     Odds are the ratio of XP to MP is probably 10:1
or greater.  

> Now, that said, I'm probably going to buy MPs when I build my machine,
> as long as the price difference stays as the current low levels.
> Consider it a "warranty" or something.

...and considering AMD doesnt lag in bringing out MPs.  Right now
XP 1900s are widely available, but the highest speed MP's are 1800s.

I've heard that the AMD 762 northbridge only works up to 12.5x133
(1666MHz) so they'll hit the wall with the MPs pretty soon unless they
have an updated stepping.


  reply	other threads:[~2001-11-17  4:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 21:30 [PATCH] AMD SMP capability sanity checking Dave Jones
2001-11-16 19:42 ` Gérard Roudier
2001-11-16 21:41 ` Randy.Dunlap
2001-11-16 21:46   ` Dave Jones
2001-11-16 21:44 ` Dan Hollis
2001-11-16 22:02   ` Dave Jones
2001-11-16 21:46 ` Jeff Garzik
2001-11-16 21:59 ` Stefan Smietanowski
2001-11-16 22:11   ` Dave Jones
2001-11-16 22:37     ` Jeff Golds
2001-11-16 23:04       ` Dave Jones
2001-11-17  0:33         ` Jeff Golds
2001-11-17  0:39           ` Dave Jones
2001-11-17  0:59             ` Andreas Boman
2001-11-17  1:54             ` Mike Fedyk
2001-11-17  4:11         ` Nathan Walp
2001-11-17  4:59           ` Mark Orr [this message]
2001-11-16 23:40     ` Stefan Smietanowski
2001-11-16 23:47       ` Dave Jones
2001-11-17  1:05         ` Stefan Smietanowski
2001-11-17  1:09           ` Dan Hollis
2001-11-17  1:11             ` Dave Jones
2001-11-17  1:10           ` Dave Jones
2001-11-21  0:42 ` Pavel Machek

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=20011116225924.3390dc77.markorr@intersurf.com \
    --to=markorr@intersurf.com \
    --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