From: Larry McVoy <lm@mcvoy.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: The Eunuchs Historic Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Distributed systems, was: On the origins of Linux - "an academic question"
Date: Sun, 9 Feb 2020 10:42:56 -0800 [thread overview]
Message-ID: <20200209184256.GD21264@mcvoy.com> (raw)
In-Reply-To: <20200208171837.15CA62215C@orac.inputplus.co.uk>
On Sat, Feb 08, 2020 at 05:18:37PM +0000, Ralph Corderoy wrote:
> 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.
Or it might be a giant step backwards in terms of memory latency.
prev parent reply other threads:[~2020-02-09 18:43 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
2020-02-09 18:42 ` Larry McVoy [this message]
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=20200209184256.GD21264@mcvoy.com \
--to=lm@mcvoy.com \
--cc=ralph@inputplus.co.uk \
--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).