The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Historic Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Distributed systems, was: On the origins of Linux - "an academic question"
Date: Sat, 08 Feb 2020 17:18:37 +0000	[thread overview]
Message-ID: <20200208171837.15CA62215C@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAKzdPgz5pfeCsG61XG9Fj6UxAuTBDVYnBNQzQJB3JfQ8GKyBNg@mail.gmail.com>

Hi,

Rob Pike wrote:
> I am convinced that large-scale modern compute centers would be run
> very differently, with fewer or at least lesser problems, if they were
> treated as a single system rather than as a bunch of single-user
> computers ssh'ed together.

This reminds me of Western Digital's recent OmniXtend.  It takes a
programmable Ethernet switch and changes the protocol: Ethernet becomes
OmniXtend.  It's a cache-coherency protocol the allows CPUs, custom
ASICs, FPGAs, GPUS, ML accelerators, ... to each hang off an 802.3 PHY
and share one memory pool.
https://blog.westerndigital.com/omnixtend-fabric-innovation-with-risc-v/

It might be a step towards a room of racks being marshalled as a single
computer.

-- 
Cheers, Ralph.

  parent reply	other threads:[~2020-02-08 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18  6:15 Andrew Warkentin
2020-01-18  6:25 ` Rob Pike
2020-01-18  7:30   ` [TUHS] [TUHS -> COFF] " Andrew Warkentin
2020-01-18 11:55   ` [TUHS] " Álvaro Jurado
2020-01-20 17:05     ` U'll Be King of the Stars
2020-01-18 20:24   ` Adam Thornton
2020-01-18 20:40     ` Toby Thain
2020-01-20 20:19   ` Clem Cole
2020-02-08 17:18   ` Ralph Corderoy [this message]
2020-02-09 18:42     ` Larry McVoy

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=20200208171837.15CA62215C@orac.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    --cc=robpike@gmail.com \
    --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).