The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] (early parallel/concurrent computing) (was: unix "awesome list")
Date: Tue, 8 May 2018 20:25:08 -0400	[thread overview]
Message-ID: <016301d3e72c$2fae3680$8f0aa380$@ronnatalie.com> (raw)
In-Reply-To: <FAED01BC-5B5D-4EB7-8195-2D13F3460E51@orthanc.ca>

BRL had contracted with the Denver Electronics Corporation (Denelcor) to
build a fluid dynamic platform.   Early plans were for an analog and then
hybrid computer, but this quickly evolved into the all-digital Heterogenous
Element Procesor.   The computer was MIMD and could run 40 or so threads
simultaneously while hardware scheduling 256 times that.   Each memory
location in the main memory had a "full-empty" bit which allowed you to to
execute instructions like "Wait until Full, then Store", and the processor
handled all that.

Of course, this was about the time Mike Muuss and his band were becoming
real firecrackers in the labs.    Mike shot his mouth off  that we could put
UNIX on it (our answer to everything) and the lab management took us up on
the offer.    Perhaps, with the exception of some of the MultibusII stuff,
one of the nicest UNIX architectures around.

Mike immediately set to work.   He did the C compiler while Doug Kingson did
the assembler.   I did the loader I think.   We then started on the kernel.
Mike doing the low level stuff and the guts of the kernel and me doing all
the IO (the "dmr" directory traditionally).      About the time we got the
thing running I realized that the IO performance was terrible.    The thing
had a sidecar unit with 32 distinct unibuses which  really should have been
fast enough, except the latency to start the I/Os was about ten ops/sec.
Me and the HEP designer, Burton Smith sat down at the Golden Corral
steakhouse in Aberdeen and designed a new processor that sat on the main
memory bus.   It was built out of spare HEP parts and a PDP-11/34 that I had
lying around as the control processer.   I through in the LOS operating
system (No time for sharing -- Uniprocessor system) scavenged from my BRL
Gateway code to drive it.   In two days we had drastically increased the IO
performance.

The thing ran parallizable apps, notably Mike's BRL ray tracing "CAD"
package.    We pretty much used it to generate a movie of a shell's eye view
of a collision with a tank.   The system was replaced with a Cray XMP.

Amusingly in our machine room, awaiting arrival of the HEP were taped out
markings where all the cabinets went around a central building pillar.
Visiting the machine in the factor, it was laid out around a taped marking
showing the location of our post.

-Ron




  reply	other threads:[~2018-05-09  0:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 18:22 [TUHS] unix "awesome list" A. P. Garcia
2018-05-07 21:10 ` Dave Horsfall
2018-05-07 21:53   ` Steve Johnson
2018-05-08 12:24     ` Theodore Y. Ts'o
2018-05-08 13:51       ` Bakul Shah
2018-05-08 14:53         ` Clem Cole
2018-05-08 15:23           ` Jon Steinhart
2018-05-08 15:31           ` Steve Johnson
2018-05-08 16:32             ` Clem Cole
2018-05-08 17:33             ` Theodore Y. Ts'o
2018-05-08 18:40             ` William Cheswick
2018-05-08 21:25             ` Bakul Shah
2018-05-08 23:06             ` [TUHS] (early parallel/concurrent computing) (was: unix "awesome list") Lyndon Nerenberg
2018-05-09  0:25               ` Ron Natalie [this message]
2018-05-09  1:28                 ` Kurt H Maier
2018-05-08 21:15           ` [TUHS] unix "awesome list" Bakul Shah
2018-05-08 16:31       ` Michael Parson
2018-05-08 17:20         ` Larry McVoy
2018-05-08 17:49           ` Michael Parson
2018-05-08 20:48           ` Dave Horsfall
2018-05-08 17:53         ` Theodore Y. Ts'o
2018-05-07 21:54   ` Steve Nickolas
2018-05-08  8:14     ` Mutiny
2018-05-07 22:34 ` Andy Kosela

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='016301d3e72c$2fae3680$8f0aa380$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    /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;
as well as URLs for NNTP newsgroup(s).