From: Charles Cazabon <linux-kernel@discworld.dyndns.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Threads FAQ entry incomplete
Date: Wed, 20 Jun 2001 13:42:21 -0600 [thread overview]
Message-ID: <20010620134221.C12357@qcc.sk.ca> (raw)
In-Reply-To: <20010620104800.D1174@w-mikek2.des.beaverton.ibm.com> <lx66drf04u.fsf@pixie.isr.ist.utl.pt>
In-Reply-To: <lx66drf04u.fsf@pixie.isr.ist.utl.pt>; from yoda@isr.ist.utl.pt on Wed, Jun 20, 2001 at 07:59:29PM +0100
Rodrigo Ventura <yoda@isr.ist.utl.pt> wrote:
>
> BTW, I have a question: Can the availability of dual-CPU boards for intel
> and amd processors, rather then tri- or quadra-CPU boards, be explained with
> the fact that the performance degrades significantly for three or more CPUs?
> Or is there a technological and/or comercial reason behind?
Commercial reasons. Cost per motherboard/chipset goes way up as the number of
CPUs supported goes up. For each CPU that a chipset supports, it has to add a
lot of pins/lands, and chipsets are already typically land-limited.
Motherboard trace complexity (and therefore number of layers) goes up. Add to
that that the potential market goes down as CPUs goes up.
You can buy 4-, 8-, and 16-way motherboards for Intel CPUs (don't know about
more). But the 16-way ones will cost as much as a house.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <linux@discworld.dyndns.org>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
next prev parent reply other threads:[~2001-06-20 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 17:48 Threads FAQ entry incomplete Mike Kravetz
2001-06-20 18:59 ` Rodrigo Ventura
2001-06-20 19:42 ` Charles Cazabon [this message]
2001-06-20 23:00 ` J.D. Bakker
2001-06-20 22:53 ` Charles Cazabon
2001-06-21 0:50 ` D. Stimits
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=20010620134221.C12357@qcc.sk.ca \
--to=linux-kernel@discworld.dyndns.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.