The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Steve Johnson" <scj@yaccman.com>
To: "Doug McIlroy" <doug@cs.dartmouth.edu>, tuhs@tuhs.org
Subject: Re: [TUHS] AT&T Hardware  (3B2)
Date: Sun, 01 Jul 2018 06:29:57 -0700	[thread overview]
Message-ID: <285b5c9f6210cfbc4f2ff3a84c11e674cc230879@webmail.yaccman.com> (raw)
In-Reply-To: <201806301824.w5UIOO71062430@tahoe.cs.Dartmouth.EDU>

[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]

The 3B2 was designed for AT&T by Convergent Technologies.  I later
worked with several people at Convergent, one of whom had a framed
circuit board on his wall.  It was a wonder to behold -- the board
had wires all over it that were added later, and nearly a dozen "bugs"
-- in the days of discrete logic chips, a bug was when you took
another chip and glued it, upside down, on top of an existing chip and
then ran wires to the pins in the air.   As I recall, the story was
that the first demo of the 3B2 happened roughly six weeks after the
initial request, using the board on the wall.  Now, that's what
should really be in the computer museums...

In those days, if there was floating point it was a separate chip, and
the 3B2 had none.   Floating-point instructions caused a fault,
which meant a context switch to the OS, where the instruction was
emulated and then the program returned.   The performance, as I
recall was about 800 FLOPS - dismal.   We fixed the compiler so it
would generate calls to subroutines that did the floating point
operations, and the performance improved by over an order of magnitude
-- still dismal, but no longer ridiculous...

One of the events that led me to leave AT&T was that they fired the
head of the benchmarking group at Indian Hill, a most competent woman,
because they didn't like the results she was presenting.  When a
company's information channels stop functioning reliably, it's time to
leave...

Steve

----- Original Message -----
From: "Doug McIlroy" <doug@cs.dartmouth.edu>
To:<tuhs@tuhs.org>
Cc:
Sent:Sat, 30 Jun 2018 14:24:24 -0400
Subject:Re: [TUHS] AT&T Hardware

 Anent 3B's: Last time I visited Paul Allen's Living Computer Museum
 the only working Unix on display was running on a 3B2. Apparently
 the machine was robust if nothing else.

 doug


[-- Attachment #2: Type: text/html, Size: 2573 bytes --]

  parent reply	other threads:[~2018-07-01 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 18:24 [TUHS] AT&T Hardware Doug McIlroy
2018-07-01  1:05 ` William Corcoran
2018-07-01 13:29 ` Steve Johnson [this message]
2018-07-02  0:12   ` [TUHS] AT&T Hardware (3B2) Lyndon Nerenberg
2018-07-02  9:56   ` Kevin Bowling

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=285b5c9f6210cfbc4f2ff3a84c11e674cc230879@webmail.yaccman.com \
    --to=scj@yaccman.com \
    --cc=doug@cs.dartmouth.edu \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).