From: Andreas Bombe <bombe@informatik.tu-muenchen.de>
To: Astinus <Astinus@netcabo.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATHLON HELP ME ON THIS PLZ!!!!
Date: Thu, 3 Jan 2002 18:50:37 +0100 [thread overview]
Message-ID: <20020103175037.GC737@bombe.modem.informatik.tu-muenchen.de> (raw)
In-Reply-To: <000901c192fc$66df2b00$d500a8c0@mshome.net>
In-Reply-To: <000901c192fc$66df2b00$d500a8c0@mshome.net>
On Tue, Jan 01, 2002 at 07:42:09PM -0000, Astinus wrote:
> Can anyone explian me why almost every body, even quite big servers bought
> athlon xps instead of the mp ones^??
> This is an issue that concerns me too!! You see, ~why would a big server
> risk to buy a processor that may not work when the other one (mp) is suppose
> to work?? Is it for the extraa dollars u have to spend on the hardware???
>
> Am I w~rong?? Are the MPs and the XPs so similar that the problems u have
> with one will be the same with the other???
They are in fact the same, except for the packaging (well, one says "XP"
the other says "MP") and possibly some ID number inside.
The difference is that MPs are tested by AMD for SMP capability and
guaranteed to work (ie. if they don't work you can have it replaced).
As I detailed in another mail, XPs can basically be of three types:
1) failed MP test, sold as XP
2) not tested for MP since market demands more XPs
3) passed MP test, but market demands more XPs
XPs are cheaper than MPs so people try those in SMP configs in the hope
that there are many type 3 XPs or that they get type 2 XPs that would
have passed the MP test.
It's impossible to tell which type you actually got, so the XPs in SMP
are always one of the main suspects if there is a problem. In short,
you won't have those (CPU specific) problems with MPs. If it's other
problems (chipset, for example) they could still appear.
--
Andreas Bombe <bombe@informatik.tu-muenchen.de> DSA key 0x04880A44
prev parent reply other threads:[~2002-01-03 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 19:42 Astinus
2002-01-01 21:07 ` Mike Harrold
2002-01-01 21:19 ` Shaya Potter
2002-01-01 21:38 ` Daniel Freedman
2002-01-01 22:57 ` Brian
2002-01-02 3:32 ` Andre Hedrick
2002-01-03 17:50 ` Andreas Bombe [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=20020103175037.GC737@bombe.modem.informatik.tu-muenchen.de \
--to=bombe@informatik.tu-muenchen.de \
--cc=Astinus@netcabo.pt \
--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
all inboxes | Powered by JetHome®