From: "J.D. Bakker" <bakker@thorgal.et.tudelft.nl>
To: Charles Cazabon <linux-kernel@discworld.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Threads FAQ entry incomplete
Date: Thu, 21 Jun 2001 01:00:19 +0200 [thread overview]
Message-ID: <a05100306b756d7a9fdac@[130.161.115.44]> (raw)
In-Reply-To: <20010620134221.C12357@qcc.sk.ca>
In-Reply-To: <20010620104800.D1174@w-mikek2.des.beaverton.ibm.com> <lx66drf04u.fsf@pixie.isr.ist.utl.pt> <20010620134221.C12357@qcc.sk.ca>
At 13:42 -0600 20-06-2001, Charles Cazabon wrote:
>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.
That's not quite accurate. Most modern SMP-able processors have a
common bus, where going from 1->2 CPUs adds just a handful of extra
nets (usually bus request, bus grant and some IRQs). The actual
issues are threefold.
First, most commodity chipsets simply support no more than two CPUs
at best; most CPUs don't support having more (or any) siblings.
Adding more is cheap on the ASIC level, but nobody bothers because
there is no demand.
Second, adding more CPUs on a shared bus decreases the bus bandwidth
that is available per CPU. This is comparable with having Ethernet
hubs vs switches. The really expensive multi-CPU boards have crossbar
switches between CPUs, memory and PCI. Future stuff like RapidIO may
mitigate this.
Third, the more CPUs a bus holds, the higher the capacitance on the
bus lines. Higher capacitance means lower maximum bus speed, which
aggravates point two.
>Motherboard trace complexity (and therefore number of layers) goes up. Add to
>that that the potential market goes down as CPUs goes up.
True enough.
Regards,
JDB
[working on a SMP PowerPC design]
--
LART. 250 MIPS under one Watt. Free hardware design files.
http://www.lart.tudelft.nl/
next prev parent reply other threads:[~2001-06-20 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 17:48 Mike Kravetz
2001-06-20 18:59 ` Rodrigo Ventura
2001-06-20 19:42 ` Charles Cazabon
2001-06-20 23:00 ` J.D. Bakker [this message]
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='a05100306b756d7a9fdac@[130.161.115.44]' \
--to=bakker@thorgal.et.tudelft.nl \
--cc=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 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®