Delay-line and drum computers (like the LGP-30, the HP 9100, and the grandmama of them all, the Pilot ACE) all sort of had to do a sort of time multiplexing; the Tera MTA I mentioned, as well as the CDC 6600's PPs (FEPs), worked that way too, time-sharing a single ALU and control unit among many register sets. That's also one of the things going in modern GPUs, but it's hard to say it's to reduce part count. Still, they'd need a lot more parts to do the same thing if they didn't do it.
This CSR/SHP thing sounds really interesting! Thank you!
I got to tour the Tera offices in Seattle in the late 90s, about all I remember is that it was a torus and it used some finicky silicon process that was leading to manufacturing delays. I was all into Beowulf and Mosix [2] at the time using Alpha or x86, so I wasn't drawn to it that much.
Tera’s first machine was bipolar (ECL I assume) and they finally squeezed out a CMOS successor with a lot of assistance from their EDA vendor. Never knew the story of why moving to CMOS was so urgent.
Amusingly, it was the Beowulf list where someone converted me to the Tera religion (rgb I think). I was convinced that was the way all computers would work soon. And, well, it's how GPUs work, kind of. But mostly I was wrong.
Not sure I agree about modularity. Galaxies, mammalian bodies, trees, bacterial films, cars, books, and river systems are modular. It would be surprising if we could make software non-modular. But we could make it only as modular as a tree.
Composition is great, scale free self similarity is probably the basis for the universe.
Modularity is a great design technique, it can also make things weaker and force other (unknowable) design choices because the module boundary prevents the flow of information/force. Overly constrained modular systems encourage globals, under constrained modular systems are asymptotic to mud/clay.
I don't want to use K8S as a strawman to attack modularity, but I think it is an example of using this powerful design tool to solve the wrong problem using mis-applied methods all the while being more complex and using more resources. In the case of designing systems, modules/objects/processes (Erlang sense) are critical, but not so much in building/engineering them. Demodularizing or fusing a design can make it more robust and more efficient.
I don't dislike modularity, I just think it is a bigger more complex topic than most give it credit for. Unix is highly-non modular and very poor composition. It sits on a molehill of a local maximum, itself sitting in the bottom of a Caldera, a sort of Wizard Mt on Wizard Island.
Other things you might like is the research around "Collapsing Towers of Interpreters" [1]
Or Dave Ackley's T2 Tile Project and Robust First Computing [2]
Would love to chat more, but internet access is spotty for the next week, non-replies are not ignores.
[1] https://lobste.rs/s/yj31ty/collapsing_towers_interpreters
[2] https://www.youtube.com/watch?v=7hwO8Q_TyCA https://www.youtube.com/watch?v=Z5RUVyPKkUg
I had a really good mentor when working on this product and I learn the importance of modularity in design. I was just off my internship doing a D2K/Oracle implementation for an airline in-cabin inventory application, so working on Spooler was a breath of fresh air.
[1] https://support.hpe.com/hpsc/doc/public/display?docId=emr_na...
I'd add the Tandem NonStop to my personal list. I don't know why I overlooked the LGP-30 [1], I'll have to find a schematic. 113 vacuum tubes is really impressive, I wonder if there is any overlap with this design and System Hyper Pipelining [2]. Do you know of other architectures that use time multiplexing to reduce part count?
What bit serial computers do you like?
Ahh, it is the Story of Mel computer, awesome.
[1] https://en.wikipedia.org/wiki/LGP-30
[2] https://arxiv.org/abs/1508.07139