News for hackers. Stuff that matters.
Re:Which Machines Do Computer Architects Admire? (2013) by kragen on Wednesday January 08, 2020 @12:29AM (#21988614)
There are some really great designers on the list, like Sophie Wilson and Gordon Bell, but the list of admirable machines comes up really short — and missing a lot of really significant and admirable machines.

Maybe these are the machines bad computer architects, like Alpert, admire. Alpert is notable mostly for leading the computer industry's most expensive and embarrassing failure, the Itanic (formally known as the Itanium), despite the presence on his team of many of the world's best CPU designers, who had just come from designing the HP-PA --- a niche CPU architecture nevertheless so successful that HP's workstation competitors, such as NeXT, started using it. Earlier in his career he sunk the already-struggling 32000, the machine that by rights should have been the 68000. (And maybe if they'd funded GCC it could have been.)

What about the Tera MTA, with its massive hardware multithreading and its packet-switched RAM, which was gorgeous and prefigured significant features of the GPU explosion?

What about the DG Nova, with its bitslice ALU chips and horizontal-microcode instructions? What about the MuP21, with its radical on-chip dual circular stacks?

What about the HP 9100, with its dual stacks and PCB-inductance microcode, where the instruction set was the user interface?

What about the LGP-30, which managed to deliver a usable von Neumann computer with only 113 vacuum tubes (for amplification, inversion, and sequencing)?

What about the 26-bit ARM, with its conditional execution on every instruction, and packing the program status register into the program counter so it automatically gets restored by subroutine return, and, more importantly, interrupt return?

What about Thumb-2 with its unequaled code density?

What about the CM-1? Anyone can see that AVX-512 (or for that matter modern timing-attack-resistant AES implementations!) owe everything to the CM-1.

And the conspicuous omission of the Burroughs 5000 has already been noted by others.

I mean, there are some good designs on the list! But it hardly seems like a very comprehensive list of admirable designs.

Re:Which Machines Do Computer Architects Admire? (2013) by sitkack on Wednesday January 08, 2020 @12:52AM (#21988715)
It sounds like they just went around the room and asked some folks to list off some systems. I don't think a terrible amount of thought was put into this.

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

Re:Which Machines Do Computer Architects Admire? (2013) by kragen on Wednesday January 08, 2020 @01:00AM (#21988757)
NonStop is super interesting! HP has most of the old Tandem papers and manuals online still, I think, and you can see how the software and hardware co-evolved. It's mind-boggling the extent to which they designed the operating system around transactions; with things like TIP, the Transaction Internet Protocol, they did try to get wider adoption for that approach, but it's largely been forgotten. A shame, since we spend so much of our time debugging highly-concurrent distributed systems these days.

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!

Re:Which Machines Do Computer Architects Admire? (2013) by sitkack on Wednesday January 08, 2020 @01:52AM (#21988995)
I should provided a link to the Tandem tech reports [1], they make for great reading, great for the Little Gray Cells. I do think hardware supported distributed transactions would make many problems go away. Fusing what was once modular has unlocked lots of gains (ZFS), with the rise of the hypervisors and abstract VMs, we are getting there in baby steps. Modularity incurs a cost that is much higher than most people realize, if we see something that could be modular, we usually take it, but those decisions force future decisions we aren't aware of. I think someday we will view it in a similar light to OO.

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.

[1] https://www.hpl.hp.com/hplabs/index/Tandem

[2] https://en.wikipedia.org/wiki/MOSIX

Re:Which Machines Do Computer Architects Admire? (2013) by kragen on Wednesday January 08, 2020 @02:43AM (#21989236)
The other machines that I think of as being the siblings of the Tandem are the Nova (a lovely instruction set crippled by its shitty OS), the HP 3000, and of course the byte-addressed PDP-11. Despite their differences they all have a very similar flavor, reflecting a CISCy Zeitgeist when minicomputers were just beginning to cut their umbilical cords to PDP-10s and the like.

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.

Re:Which Machines Do Computer Architects Admire? (2013) by sitkack on Wednesday January 08, 2020 @04:35AM (#21989874)
I am happy you don't agree on modularity. I don't want to be correct, I want to arrive at correct conclusions. :)

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

Re:Which Machines Do Computer Architects Admire? (2013) by deepaksurti on Thursday January 09, 2020 @03:46AM (#21999543)
My first full time paid developer job was to be a Developer on the Spooler/Spooler Plus components which were part of the HP Tandem NSK.

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...

Re:Which Machines Do Computer Architects Admire? (2013) by AceJohnny2 on Wednesday January 08, 2020 @12:32AM (#21988640)
I can think of many ways you could've phrased this without being downright aggressive.
[dead]
Re:Which Machines Do Computer Architects Admire? (2013) by cma on Wednesday January 08, 2020 @01:06AM (#21988780)
Can you read the date at the top of the page? 2001. Thumb-2? And an ARM creator was interviewed as well, it is like you looked at first name on the list and just had a tantrum.
Re:Which Machines Do Computer Architects Admire? (2013) by kragen on Wednesday January 08, 2020 @01:15AM (#21988826)
The page dates from 2010 and includes input from Gordon Bell in 2008. I see Sophie's interviewed in the article, but somehow her masterpiece — likely the most widespread architecture in the world by now — isn't included in the list at the top.
Re:Which Machines Do Computer Architects Admire? (2013) by drivebyubnt on Wednesday January 08, 2020 @04:22PM (#21995933)
I'd be careful about giving too much credit to the original ARM design. In retrospect, like many early RISC designs, it was over-optimised for its original application. Most of the unique/novel features of the original ARM architecture turned out to be bad ideas in the long run. Most of them were later removed from the architecture, or persist only in backwards compatibility modes.

ARM is ubiquitous today more due to business models and historical accident than to inherent superiority of the design. (See also x86.)

Re:Which Machines Do Computer Architects Admire? (2013) by kragen on Wednesday January 08, 2020 @07:41PM (#21997393)
That's interesting! Clearly that's what happened to packing the PSW into the PC†, but what other features are you thinking of?

† though there are an awful lot of ARM processors out there today that have less than 64 MiB of program memory and need their interrupts to be fast, so I'd argue it might be a reasonable idea for many applications today if it didn't involve breaking toolchain compatibility in a subtle way

Re:Which Machines Do Computer Architects Admire? (2013) by jcranmer on Wednesday January 08, 2020 @12:47AM (#21988698)
> What about Thumb-2 with its unequaled code density?

It came out in 2003, and most of the people were queried for their opinions in 2001.

Re:Which Machines Do Computer Architects Admire? (2013) by kjs3 on Wednesday January 08, 2020 @12:44AM (#21988688)
It was never intended as a comprehensive list. Best if you actually read the article. It's been floating around for more than a decade.

Alpert is a bad architect...funny.