The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] unix "awesome list"
Date: Tue, 8 May 2018 14:40:23 -0400	[thread overview]
Message-ID: <29ECC550-9E6B-44F6-8272-79785D24F9EC@cheswick.com> (raw)
In-Reply-To: <146d3e969e94918e80c3d7dae01f0a839968e6bb@webmail.yaccman.com>

It is amazing how well pipes fit into this model, up to a point.  I once wrote a program
to generate and collate hundreds of thousands of images.  I used the  sed/grep/awk model,
with all the ease of attendant text I/O processing.

I was surprised one day to find it running twice as fast as usual.  They had doubled the number of
CPUs in the machine, and my program Just Worked.  Not bad for an idea that was 35 years old.

Of course, your fleet of processors will require different programming (CSP with go?).  I look forward
to see if your solutions are even remotely as easy and useful as the originals.  

BTW, will those processors basically be 8051s?

ches


> On 8May 2018, at 11:31 AM, Steve Johnson <scj at yaccman.com> wrote:
> 
> My company, Wave Computing, has built a chip with 16,000 8-bit processors on it.  And we have plans to build systems with up to a quarter million processors.  We are breaking ground in new ways to use hundreds of processors to solve problems very quickly.  It's a new way of thinking, and it makes your brain hurt.  But is is what the hardware is giving us, and there is at least another order of magnitude ahead before this trend starts running out of steam.
> 
> And it's exciting...
> 
> Steve

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180508/8ca0a25e/attachment.html>


  parent reply	other threads:[~2018-05-08 18:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 18:22 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 [this message]
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
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
2018-05-08 15:17 Noel Chiappa
2018-05-08 15:22 ` Warner Losh
2018-05-08 16:18 ` Arthur Krewat
2018-05-08 19:37   ` Dave Horsfall
2018-05-08 19:54     ` Grant Taylor

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=29ECC550-9E6B-44F6-8272-79785D24F9EC@cheswick.com \
    --to=ches@cheswick.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).