From: ebiederm@xmission.com (Eric W. Biederman)
To: John Bradford <john@grabjohn.com>
Cc: jgarzik@pobox.com (Jeff Garzik),
Herman@wirelessnetworksinc.com, linux-kernel@vger.kernel.org
Subject: Re: Open source hardware
Date: 17 Jan 2003 09:32:43 -0700 [thread overview]
Message-ID: <m165sng2j8.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200301162225.h0GMP0YI003249@darkstar.example.net>
John Bradford <john@grabjohn.com> writes:
> Do you know of anybody who has actually made a prototype board from
> any of these CPU designs? Is my idea of running a lot of simple CPUs
> together fundamentally flawed, or is it possible to overcome the
> inefficiencies of SMP, if the CPUs are designed for it from the ground
> up?
The fundamental problem is not inefficiencies of SMP. But rather
there are some tasks that simply do not parallelize well. Big
supercomputer kinds of applications that require a lot of number
crunching usually benefit from multiple cpus. But small every day
applications don't. The only applications that scale perfectly with
the number of cpus are the embarrassingly parallel ones, in which no
communication is involved between the various subtasks.
This is not to say an elegant design might not get there, AMD is
trying for that. But simple brute force will certainly not get you
there.
Eric
next prev parent reply other threads:[~2003-01-17 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 17:11 Open source hardware John Bradford
2003-01-16 17:36 ` Jeff Garzik
2003-01-16 22:25 ` John Bradford
2003-01-17 16:32 ` Eric W. Biederman [this message]
2003-01-16 21:48 ` Herman Oosthuysen
2003-01-17 9:36 ` Remco Post
2003-01-17 10:04 ` John Bradford
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=m165sng2j8.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Herman@wirelessnetworksinc.com \
--cc=jgarzik@pobox.com \
--cc=john@grabjohn.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