From: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: floating point exception
Date: Wed, 16 Jan 2002 06:28:08 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.33.0201160612360.27975-100000@shell1.aracnet.com> (raw)
In-Reply-To: <3C45858E.39F31DBA@didntduck.org>
On Wed, 16 Jan 2002, Brian Gerst wrote:
> Last I checked, Athlon XP's weren't certified for SMP, only MP's.
> That's likely what the problem is. And for the record, Tyan also
> makes Intel boards too.
>
> Processor manufacturing 101: All processors of a given family come
> off the same production line. Due to variations in the process, some
> processors have defects that only show up at higher clock speeds, SMP
> mode, etc. At the end of the line the processor is tested. If it
> fails at higher clock speeds it is marked at a lower speed. If it
> fails SMP it is marked as an XP. Market demand can also cause a chip
> to be rated lower than it really is, so you can sometimes get away
> with overclocking, etc. but it's just random luck if it really works.
Could you be more specific on this "random luck" bit? Let's say we have
a production line making processors that should *all* run SMP at, say,
1800 MHz. What fraction of them will actually run SMP and 1800? What
fraction of them will actually run at 1800 UP? What fraction of them
will run at 1700 SMP, 1600 SMP, etc.? And what fraction of them run at
1800 SMP at the end of the line but croak when they get stuck in
<ducking> Aunt Tillie's motherboard?
I'm not looking for anyone's proprietary yield statistics here -- just a
rough idea of what kind of distributions we're dealing with here. For my
application, the 1.3 GHz Athlon I've got now is overkill. I wanted a
dual when I got the system last March, but there weren't any
motherboards available that I could find.
--
M. Edward Borasky
znmeb@borasky-research.net
The COUGAR Project
http://www.borasky-research.com/Cougar.htm
Q. How do you tell when a pineapple is ready to eat?
A. It picks up its knife and fork.
next prev parent reply other threads:[~2002-01-16 14:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 12:43 Christian Thalinger
2002-01-15 23:28 ` Brian Gerst
2002-01-16 11:45 ` Christian Thalinger
2002-01-16 11:58 ` Dave Jones
2002-01-16 20:06 ` Christian Thalinger
2002-01-16 13:14 ` Bruce Harada
2002-01-17 19:26 ` bill davidsen
2002-01-16 13:52 ` Brian Gerst
2002-01-16 14:28 ` M. Edward (Ed) Borasky [this message]
2002-01-14 10:56 Zwane Mwaikambo
2002-01-14 21:26 ` Christian Thalinger
2002-01-15 14:34 ` Zwane Mwaikambo
2002-01-15 14:46 ` Richard B. Johnson
2002-01-15 18:19 ` Christian Thalinger
2002-01-15 18:31 ` Richard B. Johnson
2002-01-15 18:49 ` Christian Thalinger
2002-01-16 5:45 ` Zwane Mwaikambo
2002-01-16 11:55 ` Christian Thalinger
2002-01-16 14:32 ` Zwane Mwaikambo
2002-01-16 20:26 ` Christian Thalinger
2002-01-16 21:23 ` Richard B. Johnson
2002-01-16 21:59 ` Brian Gerst
2002-01-16 22:05 ` Richard B. Johnson
2002-01-16 22:12 ` Mark Zealey
2002-01-16 22:23 ` Richard B. Johnson
2002-01-16 23:35 ` Christian Thalinger
2002-12-27 14:18 Floating Point Exception Nandakumar NarayanaSwamy
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=Pine.LNX.4.33.0201160612360.27975-100000@shell1.aracnet.com \
--to=znmeb@aracnet.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
all inboxes | Powered by JetHome®