The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] ATC/OSDI'21 joint keynote: It's Time for Operating Systems to Rediscover Hardware (Timothy Roscoe)
Date: Fri, 17 Sep 2021 11:34:07 -0700	[thread overview]
Message-ID: <242A20E1-3A22-4C98-8D96-02C3662724D4@iitbombay.org> (raw)
In-Reply-To: <202109171751.18HHpcAf3401326@darkstar.fourwinds.com>

On Sep 17, 2021, at 10:51 AM, Jon Steinhart <jon@fourwinds.com> wrote:
> 
> Bakul Shah writes:
>> I have mixed feelings about this. Unix didn't "throw away"
>> the mainframe world of computing. It simply created a new
>> ecosystem, more suited for the microprocessor age. For IBM it
>> was perhaps the classic Innovator's Dilemma. Similarly now we
>> have (mostly) the Linux ecosystem, while the actual hardware
>> has diverged a lot from the C memory model. There are
>> security issues. There is firmware running on these system
>> about which the OS knows nothing. We have processors like
>> Esperanto Tech's 1088 64 bit Risc-V cores, each with its own
>> vector/tensor unit, 160MB onchip sram and 23.8B transistors
>> but can take only limited advantage of it. We have super
>> performant GPUs but programming them is vendor dependent and
>> a pain. If someone can see a clear path through all this,
>> and create a new software system, they will simply generate a
>> new ecosystem and not worry about 50 years worth of work.
> 
> You're kind of reminding me of the HEP (heterogeneous element
> processor) talk that I saw at I think Usenix in Santa Monica.
> My opinion is that it was a "kitchen sink" project - let's
> throw in a few of these and a few of those and so on.  Also
> analogous to what I saw in the housing market up here when
> people started cashing in their California huts for Oregon
> mansions - when we lived in California we could afford two
> columns out front but now we can afford 6 columns, 8 poticos,
> 6 dormers, 4 turrets, and so on.  Just because you can built
> it doesn't keep it from being an ugly mess.
> 
> So my question on many of these processors is, has anybody
> given any thought to system architecture?  Most likely all
> of us have had to suffer with some piece of spiffy hardware
> that was pretty much unprogrammable.  Do the performance
> numbers mean anything if they can't be achieved in an actual
> system configuration?

If you look at the chip architecture, it is pretty regular.
    https://www.esperanto.ai/technology/
and very low power (0.01W/core as opposed to 7W/core on X86-64)
     https://www.servethehome.com/esperanto-et-soc-1-1092-risc-v-ai-accelerator-solution-at-hot-chips-33/

The equivalent of turrets and porticos and columns and dormers
are IO ports like USB, ethernet, and various GPIOs etc. but they
use only a small portion of the available gates.

IMHO the real issue is that the software folks are *not* providing
and *can no*t provide any sort of guidance for general purpose
computing, as the memory underlying modern programming languages
is so far removed from reality. The situation is sorta like what
happens with people with newly acquired incredible wealth but no
background in how to spend or manage it wisely (and I don't mean
*investing* to get more wealth). At least in that case there are
people who can help you and a tremendous need. Here we can put
billions and billions of gates on a chip and even do wafer scale
integration but these gates are not fungible like money.


  parent reply	other threads:[~2021-09-17 18:34 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 21:58 Dan Cross
2021-09-02  8:42 ` Tony Finch
2021-09-03  0:19   ` John Cowan
2021-09-03  3:24     ` Douglas McIlroy
2021-09-03 13:21       ` Theodore Ts'o
2021-09-08 11:14         ` Tony Finch
2021-09-16 19:27         ` Dan Cross
2021-09-17  0:34           ` Theodore Ts'o
2021-09-17  0:44             ` Larry McVoy
2021-09-17 17:07               ` Bakul Shah
2021-09-17  1:33             ` Dan Cross
2021-09-02 15:41 ` Kevin Bowling
2021-09-02 20:12   ` Marshall Conover
2021-09-03 15:56 ` Warner Losh
2021-09-03 17:10   ` Adam Thornton
2021-09-03 17:28     ` Larry McVoy
2021-09-03 17:42       ` John Floren
2021-09-03 19:02       ` Lawrence Stewart
2021-09-03 19:11       ` Clem Cole
2021-09-03 17:46     ` [TUHS] ATC/OSDI'21 joint keynote: It's Time for Operating Systems to Rediscover Hardware [ really a comment on SoCs ] Jon Steinhart
2021-09-16 18:38 ` [TUHS] ATC/OSDI'21 joint keynote: It's Time for Operating Systems to Rediscover Hardware (Timothy Roscoe) Dan Cross
2021-09-16 19:34   ` Jon Steinhart
2021-09-16 19:41     ` Larry McVoy
2021-09-16 23:14       ` Marshall Conover
2021-09-16 23:44         ` Rob Pike
2021-09-17  0:37           ` Larry McVoy
2021-09-17  1:38         ` Jon Steinhart
2021-09-17  3:54         ` John Cowan
2021-09-16 23:45       ` Jon Steinhart
2021-09-17  0:06         ` Al Kossow
2021-09-17  4:06           ` John Cowan
2021-09-17  4:18             ` Al Kossow
2021-09-17  0:32         ` Larry McVoy
2021-09-16 23:54       ` David Arnold
2021-09-17  1:10         ` Jon Steinhart
2021-09-17  1:28           ` Larry McVoy
2021-09-17  1:40             ` Jon Steinhart
2021-09-17  2:04               ` Larry McVoy
2021-09-17  2:21                 ` Jon Steinhart
2021-09-17  2:48           ` Theodore Ts'o
2021-09-17 17:39         ` Bakul Shah
2021-09-17 17:51           ` Jon Steinhart
2021-09-17 18:07             ` Larry McVoy
2021-09-17 21:03               ` Derek Fawcus
2021-09-17 22:11                 ` Larry McVoy
2021-09-19  4:05                   ` Theodore Ts'o
2021-09-17 18:34             ` Bakul Shah [this message]
2021-09-17 18:56               ` Jon Steinhart
2021-09-17 19:16                 ` Bakul Shah
2021-09-17 19:35                   ` Jon Steinhart
2021-09-17 15:56     ` Bakul Shah
2021-09-17 18:24       ` ron minnich

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=242A20E1-3A22-4C98-8D96-02C3662724D4@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=tuhs@minnie.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).