All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Martin <rmartin@CS.Berkeley.EDU>
To: ultralinux@vger.kernel.org
Subject: Re: Ultra AXmp
Date: Sun, 26 Jul 1998 00:45:53 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531079@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222358531013@msgid-missing>


I'm not sure this dicussion belongs on this list, but I'll provide an
alternate opinion to liven the debate. 

> It has been hard to communicate computer scientists (:-) since most of them
> do not understand what PDE stands for. ;-) To put it in short, the difficulty

Yup! All we get from the scientists is something like "please solve my 
Ax=b fast. Oh yea, I have a some funny structure in my A and b too". 

> numerical problems are not in that category. Searching for low-latency,
> high-throughput inter-processor communication should be still listed high
> on our agenda. At least this is my view.

Actually, anything that can be expressed in terms of large linear
algebra operations is a good candidate for a Beowulf style system. 
There has been endless work on MPPs and recently, clusters in this area.
Now there are plenty of good latency tolerating algorithms for most 
common operations. 

Dissecting the NAS Parallel Benchmarks on our cluster has convinced me that
these codes can run over a high bandwidth TCP just fine. On our 64 node
UltraSparc/Myrinet cluster, most of the NPB codes spent 5%-15% of the
time in communication. FT (a 3D FFT), the program that stresses the 
network the most, is just a bandwidth hog (high bandwidth alone is not an
interesting CS problem). FT, like all the other NPB codes, can tolerate 
huge software overheads and network latencies. 

Hardly worth investing time or $$$ in a communication network when you're
only spending 15% of the time there! If the NPB aren't representative,
well, that's another problem  ... 

I'm more and more convinced that inter-processor communication is no 
longer a first order issue. Focusing on memory system efficiency 
(effective use of the cache and memory BW) will get you much more bang for
your buck. Even in the parallel case, I would spend money on huge L2
caches and memory bandwidth over processor interconnect. 

My humble $0.02 worth... 

						-Rich

  parent reply	other threads:[~1998-07-26  0:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-11 18:36 Ultra AXmp Bob Drzyzgula
1998-07-12  1:56 ` David S. Miller
1998-07-12  2:21 ` Matthew Jacob
1998-07-12  2:29 ` David S. Miller
1998-07-12  5:02 ` Matthew Jacob
1998-07-12 12:54 ` Douglas Eadline
1998-07-12 23:59 ` Bob Drzyzgula
1998-07-13  6:27 ` Qiru Zhou
1998-07-13  6:38 ` David S. Miller
1998-07-13 10:40 ` Bob Drzyzgula
1998-07-13 12:09 ` Xavier Beaudouin
1998-07-13 13:59 ` Robert G. Brown
1998-07-13 14:29 ` Robert HYATT
1998-07-13 14:54 ` Matthew Jacob
1998-07-13 14:56 ` Matthew Jacob
1998-07-13 14:59 ` Matti Aarnio
1998-07-13 15:24 ` Robert HYATT
1998-07-13 15:38 ` Robert HYATT
1998-07-13 16:56 ` Robert G. Brown
1998-07-13 17:04 ` Robert G. Brown
1998-07-13 17:13 ` Lawrence D. Lopez
1998-07-13 17:26 ` Mike
1998-07-14  1:44 ` Shannon
1998-07-14  7:00 ` David S. Miller
1998-07-14 18:07 ` Douglas Eadline
1998-07-14 23:23 ` Bob Drzyzgula
1998-07-15  3:31 ` Dave Wreski
1998-07-15  8:07 ` Ward Deng
1998-07-15 11:14 ` Bob Drzyzgula
1998-07-15 11:27 ` David S. Miller
1998-07-15 15:54 ` Robert G. Brown
1998-07-15 17:11 ` Robert G. Brown
1998-07-15 23:22 ` Luis Ponce de Leao
1998-07-21 23:29 ` Ward Deng
1998-07-25 23:34 ` Ward Deng
1998-07-26  0:02 ` Ward Fenton
1998-07-26  0:45 ` Rich Martin [this message]
1998-07-26  3:34 ` Bob Drzyzgula
1998-07-26  4:00 ` Ward Deng
1998-07-26  4:29 ` Ward Deng
1998-07-26 12:29 ` Bob Drzyzgula
1998-07-26 13:57 ` Douglas Eadline

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=marc-linux-ultrasparc-90222358531079@msgid-missing \
    --to=rmartin@cs.berkeley.edu \
    --cc=ultralinux@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.