The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ATC/OSDI'21 joint keynote: It's Time for Operating Systems to Rediscover Hardware (Timothy Roscoe)
Date: Fri, 03 Sep 2021 17:42:33 +0000	[thread overview]
Message-ID: <jWERV-CRMZaEztKLxz8vpQGy0xf4aM3BZZo6coP_MDXfJGCxKobJfmOeqbXBPOEwz9YtFg1AfdY5JwPL5jbgQsHrlb7k-FQlt5tJpsI6k1E=@jfloren.net> (raw)
In-Reply-To: <20210903172848.GF13471@mcvoy.com>

When I took Computer Architecture, "reasoning" about out-of-order execution involved 30-page worksheets where we could track the state of the Tomasulo algorithm through each iteration. It was ludicrously slow work, and wouldn't be a lot of fun even if you had a computerized tool to help step through things instead.

If you're talking about a modern Intel CPU where your compiler emits CISC instructions which are actually implemented in RISC instructions in the microcode, which in turn get rewritten and reordered internally by the CPU... it's hard to fault programmers for thinking at the level of the instruction set that's presented to them, even if it looks like a PDP-11.

The above should not be read as an endorsement of the CPU status quo, of course :)

john

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, September 3rd, 2021 at 10:28 AM, Larry McVoy <lm@mcvoy.com> wrote:

> I am exactly as Adam described, still thinking like it is a PDP-11.
>
> Such an understandable machine. For me, out of order execution kind
>
> of blew up my brain, that's when I stopped doing serious kernel work,
>
> I just couldn't get to a mental model of how you reasoned about that.
>
> Though I was talking to someone about it, maybe Clem, recently and
>
> came to the conclusion that it is fine, we already sort of had this
>
> mess with pipelines. So maybe it is fine, but out of order bugs my
>
> brain.
>
> On Fri, Sep 03, 2021 at 10:10:57AM -0700, Adam Thornton wrote:
>
> > Much of the problem, I think, is that:
> >
> > 1.  an idealized PDP-11 (I absolutely take Warner's point that that
> >
> >     idealization never really existed) is a sufficiently simple model that a
> >
> >     Bear Of Little Brain, such as myself, can reason about what's going to
> >
> >     happen in response to a particular sequence of instructions, and get fairly
> >
> >     proficient in instructing the machine to do so in a non-geological
> >
> >     timeframe.
> >
> > 2.  a modern CPU? Let alone SoC? Fuggedaboutit unless you're way, way
> >
> >     smarter than I am. (I mean, I do realize that this particular venue has a
> >
> >     lot of those people in it...but, really, those are people with
> >
> >     extraordinary minds.)
> >
> >
> > There are enough people in the world capable of doing 1 and not 2 that we
> >
> > can write software that usually mostly kinda works and often gets stuff
> >
> > done before collapsing in a puddle of nasty-smelling goo. There aren't
> >
> > many people at all capable of 2, and as the complexity of systems
> >
> > increases, that number shrinks.
> >
> > In short, this ends up being the same argument that comes around every so
> >
> > often, "why are you people still pretending that the computer is a PDP-11
> >
> > when it clearly isn't?" Because, as with the keys and the streetlight,
> >
> > that's what we have available to us. Only a grossly oversimplified model
> >
> > fits into our heads.
> >
> > Adam
> >
> > On Fri, Sep 3, 2021 at 8:57 AM Warner Losh imp@bsdimp.com wrote:
> >
> > > On Wed, Sep 1, 2021 at 4:00 PM Dan Cross crossd@gmail.com wrote:
> > >
> > > > I'm curious about other peoples' thoughts on the talk and the overall
> > > >
> > > > topic?
> > >
> > > My comment is that the mental map that he presents has always been a lie.
> > >
> > > At least it's been a lie from a very early time.
> > >
> > > Even in Unibus/Qbus days, the add-in cards had some kind of processor
> > >
> > > on it from an early time. Several of the VAX boards had 68000 or similar
> > >
> > > CPUs that managed memory. Even the simpler MFM boards had buffer
> > >
> > > memory that needed to be managed before the DMA/PIO pulled it out
> > >
> > > of the card. There's always been an element of different address spaces
> > >
> > > with different degrees of visibility into those address spaces.
> > >
> > > What has changed is all of these things are now on the SoC die so
> > >
> > > you have good visibility (well, as good as the docs) into these things.
> > >
> > > The number of different things has increased, and the for cross domain
> > >
> > > knowledge has increased.
> > >
> > > The simplistic world view was even inaccurate at the start....
> > >
> > > Warner
>
> Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm

  reply	other threads:[~2021-09-03 17:48 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 [this message]
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
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='jWERV-CRMZaEztKLxz8vpQGy0xf4aM3BZZo6coP_MDXfJGCxKobJfmOeqbXBPOEwz9YtFg1AfdY5JwPL5jbgQsHrlb7k-FQlt5tJpsI6k1E=@jfloren.net' \
    --to=john@jfloren.net \
    --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).