6 ms·
The Soul of an Old Machine: Revisiting the Timeless von Neumann Architecture
- 082349872349872 2y agothe paper: https://www.ias.edu/sites/default/files/library/Prelim_Disc_Logical_Design.pdf https://www.ias.edu/sites/default/files/library/Prelim_Disc_... > 6.8.5 ... There should be some means by which the computer can signal to the operator when a computation has been concluded. Hence an order is needed ... to flash a light or ring a bell. (later operators would discover than an AM radio placed near their CPU would also provide audible indication of process status)
- jagged-chisel 2y agoI have experienced two or three computers in my life (and least one laptop) that produced barely audible sound when CPU activity changed. The most memorable was a PowerBook G4 with a touchpad, and as I slid my finger slowly across the pad in a quiet enough room, I could hear kind of a tick each time the pointer moved a pixel.
- simne 2y agoThis was very common with first sound cards (at least on PC). As I remember, only with Creative Sound Blaster, completely finished era of continuous hearing of "machine soul" sounds.
- dantondwa 2y agoStill happens to me when using software that is GPU intensive, like Blender. When I drag a slider, I hear the buzzing of the GPU.
- Arainach 2y agoThat's not what's being described in this thread. You're referring to fan noise; the other comments are discussing electrical interference.
- camtarn 2y agoNot necessarily. My GPU audibly sings in the KhZ range whenever it comes off idle, a long time before the fans actually start up. It could be electrical noise from the fan drivers and/or motor coils if they're running at low speed, but it's definitely not the sound of air movement. And if you're e.g. processing photos on the GPU, you can hear it starting and stopping, exactly synced to the progress of each photo in the UI.
- magicalhippo 2y agoSimilarly, on-board soundcards are notorious for this. Even in my relatively recent laptop I can judge activity by the noise in my headphones if I use the built-in soundcard, thanks to electrical interference. Especially on one motherboard I had, I could relatively accurately monitor CPU activity this way. There's also audible noise that can sometimes be heard from singing capacitors[1] and coil whine[2], as mentioned in a sibling comment. [1]: https://product.tdk.com/system/files/contents/faq/capacitors-0031/singing_capacitors_piezoelectric_effect.pdf https://product.tdk.com/system/files/contents/faq/capacitors... [2]: https://en.wikipedia.org/wiki/Electromagnetically_induced_acoustic_noise https://en.wikipedia.org/wiki/Electromagnetically_induced_ac...
- mycall 2y agoI jokingly refer to my GPU's coil whine as a HDD emulator as it sounds like a spinning disk to me.
- RGamma 2y agoDepending on workload my mainboard's VRMs (I think) sound like birds chirping.
- magicalhippo 2y agoThe voltage regulators are really just buck converters[1], one per phase, and so contain both capacitors and inductors in a highly dynamic setting. Thus they're very prone to the effects mentioned. [1]: https://en.wikipedia.org/wiki/Buck_converter https://en.wikipedia.org/wiki/Buck_converter
- dapperdrake 2y agoThere was a Lenovo docking station compatible with the T420 (around 2012). The headphone Jack had shrieky noise on it whenever the Gigabit Ethernet connection got going. Took a while to figure that one out. The other two docking stations were built differently and had the wires run somewhere else. EDIT: Typo
- 2y ago
- ysleepy 2y agoSome computers ship with an implementation of this using inductor coils which whine depending on the load :D
- wglb 2y agoI remember doing this back on the IBM 1130. We didn't see that there was any value in using it as a monitor.
- philiplu 2y agoMuch of my earliest computer experience was on an 1130 clone, the General Automation 18/30. Never did the AM radio thing, but you could see what phase the Fortran compiler was up to just by the general look of the blinkenlights.
- jjkaczor 2y agoMy favourite was troubleshooting an already ancient original IBM XT in 1992... The operator was complaining about the screen giving her headaches. Sure enough - when I went onsite to assist, that "green" CRT was so incredibly wavy, I could not understand how she could do her job at all. First thing I tried was moving it away from the wall, in-case I had to unplug it to replace. It stopped shimmering and shifting immediately. Moved it back - it started again. That's when we realised that her desk was against a wall hiding major electrical connectivity to the regional Bell Canada switching data-centre on the floors above her. I asked politely if she could have her desk moved - but no... that was not an option... ... So - I built my first (but not last) solution using some tin-foil and a cardboard box that covered the back and sides of her monitor - allowing for airflow... It was ugly - but it worked, we never heard from her again. My 2nd favourite was with GSM mobile devices - and my car radio - inevitably immediately before getting a call, or TXT message (or email on my Blackberry), if I was in my car and had the radio going, I would get a little "dit-dit-dit" preamble and know that something was incoming... (hahahaha - I read this and realise that this is the new "old man story", and see what the next 20-30 years of my life will be, boring the younglings with ancient tales of tech uselessness...)
- glhaynes 2y agoMy 2nd favourite was with GSM mobile devices - and my car radio - inevitably immediately before getting a call, or TXT message (or email on my Blackberry), if I was in my car and had the radio going, I would get a little "dit-dit-dit" preamble and know that something was incoming... I remember this happening all the time in meetings. Every few minutes, the conversation would stop because a phone call was coming in and all the conference room phones started buzzing. One of those things that just fades away so you don't notice it coming to an end.
- mrandish 2y agoAt a certain large tech company, at the peak of GSM data-capable phones (eg Palm Treo, Blackberry) it was accepted practice for everyone turn off data or leave their phone on a side table due to conference speaker phones on the tables amplifying the data. Also, during this era I was on a flight and the pilot came over the PA right before pushing from the gate saying exasperatedly "Please turn your damn phones off!" (I assumed the same RF noise was leaking into his then-unsheilded headset).
- vincent-manis 2y agoMany years ago, I was a user of an IBM 1130 computer system. It filled a small room, with (as I recall) 16K 16-bit words and a 5MB disk drive, which was quite noisy. I would feed in my Fortran program, then head down to the other end of the building to get coffee. The computer would think about the program for a while, and then start writing the object file. This was noisy enough that I'd hear it, and head back to the computer room just in time to see the printer burst into action. (Please feel free to reference the Monty Python “Four Yorkshiremen” sketch. But this really happened.)
- alejohausner 2y agoAhh… the good old days. Usually when I walked all the way to the computer center to pick up my printout, it would say “syntax error on line 1”. The. I had to walk all the way back to the terminal room, and was a lot more careful the next time.
- simne 2y ago> 10^5 flip-flops is about 12.2KiB of memory It is reasonable amount for CISC CPU cache, as for CISC normal to have small number of registers (RISC is definitely multiple-register machine, as memory operations are expensive with RISC paradigm).
- Someone 2y agoI don’t think that’s correct. Ideally, your working set fits into the cache, and that doesn’t get smaller or larger when you use a RISC CPU. (There may be an effect because of instruction density, but that’s not very big, and will have less of an effect the larger your working set)
- simne 2y ago> Ideally, your working set fits into the cache Ideally, your working set fits into the registers, and that was most win feature or RISC, having relatively simple hardware (if compared to genuine CISC, like IBM-360 mainframes) they saved significant space on chip for more registers. - Register-register operations are definitely avoid memory wall, so data cache become insignificant. Sure, if we compare comparable, not apples vs carrots.
- simne 2y agoIf you are unlucky, so your working set don't fit into the registers, in this case you sure will deal with memory bus and with cache hierarchy. But best if you just don't touch memory at all, making all processing in your code in registers.
- Joker_vD 2y ago> for CISC normal to have small number of registers A very common fallacy. For CISC it's normal to have small number of programmer-visible (architectural) registers. But nothing stops them from having large register files having about a hundred or two of physical registers which are renamed during the execution. IBM has been doing this sort of thing since the late sixties. Modern x64 have IIRC 180 integer general-purpose registers, and I imagine this number can be increased further: say, AMD's Am29000 from 1985 had 192 registers... and honestly, having more than 16 programmer-visible registers is not that useful when 99.999% of the code is written for the high-level languages with separate-compilation schemes: any function call requires you to spill all your live data from the registers to the memory; having call-preserved registers means that you can do such a spill only once, at the start of the outer function, but it still has to happen. And outside of the function calls, in the real world programs most of the expressions that use only built-in operators either don't require more than 4 registers calculate, or can be done much more efficiently using vector/SIMD instructions and registers anyway.
- mikewarot 2y agoIf you've read the article, and thought to yourself... I wonder what it was like back then, and if there might be some other direction it could have gone, oh boy do I have a story (and opportunity) for you! It's my birthday today(61)... I'm up early to get a tooth pulled, and I read this wonderful story, and all I have is a tangent I hope some of you think is interesting. It would be nice if someone who isn't brain-foggy could run with the idea and make the Billion dollars or so I think can be wrung out of it. You get a bowl of spaghetti, that could contain the key to Petaflops, secure computing, and a new universal solvent of computing like the Turing machine, as an instructional model. The BitGrid is an FPGA without all the fancy routing hardware, that being replace with a grid of latches... if fact, the whole chip would consist almost entirely of D flip-flops and 16:1 multiplexers. (I lack the funds to do a TinyTapeout, but started going there should the money appear) All the computation happens in cells that are 4 bit in, 4 bit out Look up tables. (Mostly so signals can cross without XOR tricks, etc) For the times you need a chunk of RAM, the closest I got is using one of the tables as a 16 bit wide shift register, which I've decided to call isolinear memory[6] You can try the online React emulator I'm still working on [1], and see the source[2]. Or the older one I wrote in Pascal, that's MUCH faster[3]. There's a writeup from someone else about it as an Esoteric Language[4]. I've even written a blog about it over the years.[5] It's all out in public, for decades up to the present... so it should be easy to contest any patents, and keep it fun. I'm sorry it's all a big incoherent mess.... completely replacing an architecture is freaking hard, especially when confronted with 79 years of optimization in another direction. I do think it's possible to target it with LLVM, if you're feeling frisky. [1] https://mikewarot.github.io/bitgrid-react-app/ https://mikewarot.github.io/bitgrid-react-app/ [2] https://github.com/mikewarot/bitgrid-react-app https://github.com/mikewarot/bitgrid-react-app [3] https://github.com/mikewarot/Bitgrid https://github.com/mikewarot/Bitgrid [4] https://esolangs.org/wiki/Bitgrid https://esolangs.org/wiki/Bitgrid [5] https://bitgrid.blogspot.com/ https://bitgrid.blogspot.com/ [6] https://bitgrid.blogspot.com/2024/09/bitgrid-and-isolinear-memory.html https://bitgrid.blogspot.com/2024/09/bitgrid-and-isolinear-m...
- NetOpWibby 2y agoHappy birthday! I have no idea what you’re talking about but I’m gonna follow these links.
- WillAdams 2y agoFor those who don't recognize the title, this is a reference to the classic: https://www.goodreads.com/book/show/7090.The_Soul_of_a_New_Machine https://www.goodreads.com/book/show/7090.The_Soul_of_a_New_M... which was one of the first computer books I ever read --- I believe in an abbreviated form in _Reader's Digest_ or in a condensed version published by them (can anyone confirm that?) EDIT: or, maybe I got a copy from a book club --- if not that, must have gotten it from the local college after prevailing upon a parent to drive me 26 miles to a nearby town....
- bayouborne 2y ago“I am going to a commune in Vermont and will [In my mind I've always heard a 'henceforth' inserted here for some reason] deal with no unit of time shorter than a season” One of my favorite quotes in the book - when an overworked engineer resigns from his job at DG. The engineer, coming off a death march, leaves behind a note on his terminal as his letter of resignation. The incident occurs during a period when the microcode and logic were glitching at the nanosecond level.
- rjsw 2y agoHe didn't join a commune though, still working [1]. [1] http://www.polybus.com/hdlmaker/Resume.html http://www.polybus.com/hdlmaker/Resume.html
- cmrdporcupine 2y agoWow, I love that web page / resume and that era of HTML authorship. Brings back memories.
- toast0 2y agoHis resume doesn't really indicate he didn't join a commune. Leaving Data General in 1979 and joining ComputerVision in 1979 wouldn't preclude joining a commune for a season. However, a letter to the editor in 1981 [1] provides evidence that he left Data General specifically to work for ComputerVision, with both events happening in Spring. [1] https://www.nybooks.com/articles/1982/02/18/man-and-supermini/ https://www.nybooks.com/articles/1982/02/18/man-and-supermin...
- drcwpl 2y agoThis is a great read. von Neumann was pivotal in the design of architecture, I think his contribution is way under appreciated - did you know he also wrote a terrific book The Computer and the Brain and coined the term the Singularity? https://onepercentrule.substack.com/p/the-architect-of-tomorrow https://onepercentrule.substack.com/p/the-architect-of-tomor...
- defphysics 2y agoI see this in wikipedia: "The attribution of the invention of the architecture to von Neumann is controversial, not least because Eckert and Mauchly had done a lot of the required design work and claim to have had the idea for stored programs long before discussing the ideas with von Neumann and Herman Goldstine[3]" https://en.wikipedia.org/wiki/Von_Neumann_architecture https://en.wikipedia.org/wiki/Von_Neumann_architecture
- jazzyjackson 2y agoYes, von Neumann was tasked with doing a write up of what Eckert and Mauchly were up to in the course of their contract building the eniac/edvac. meant to be an internal memo. goldstein leaked the memo and the ideas inside were attributed to the author, von Neumann. this prevented any of the work being patented btw, since the memo served as prior art. The events are covered in great detail in Jean Jennings Bartik's autobiography "Pioneer Programmer", according to her von Neumann really wasn't that instrumental to this particular project, nor did he mean to take credit for things -- it was others that were big fans of his that hyped up his accomplishments. I attended a lecture by Mauchly's son, Bill, "History of the ENIAC", he explains how eniac was a dataflow computer that, when it was just switches and patch cables, could do operations in parallel. There's a DH Lehmer quote, "This was a highly parallel machine, before von Neumann spoiled it." https://youtu.be/EcWsNdyl264 https://youtu.be/EcWsNdyl264
- userbinator 2y agoI think the stored-program concept was also present internally at IBM around those times, although as usual no single person got the credit for that: https://en.wikipedia.org/wiki/IBM_SSEC https://en.wikipedia.org/wiki/IBM_SSEC
- mannykannot 2y agoI like the idea of identifying ‘bit flips’ in papers, which are (if I am following along) statements which precipitate or acknowledge a paradigm shift. Perhaps the most important bit-flip of this paper’s time (and perhaps first fully realized in it) might be summarized as ‘instructions are data.’ This got me thinking: today, we are going through a bit-flip that might be seen as a follow-on to the above: after von Neumann, programs were seen to be data, but different from problem/input data, in that the result/output depends on the latter, but only through channels explicitly set out by the programmer in the program. This is still true with machine learning, but to conclude that an LLM is just another program would miss something significant, I think - it is training, not programming, that is responsible for their significant features and capabilities. A computer programmed with an untrained LLM is more closely analogous to an unprogrammed von Neumann computer than it is to one running any program from the 20th. century (to pick a conservative tipping point.) One could argue that, with things like microcode and virtual machines, this has been going on for a long time, but again, I personally feel that this view is missing something important - but only time will tell, just as with the von Neumann paper. This view puts a spin on the quote from Leslie Lamport in the prologue: maybe the future of a significant part of computing will be more like biology than logic?
- Pannoniae 2y agoAnd the next paradigm shift after that will probably be "programs' own outputs are their input"
- cmontella 2y agoThat sounds like a feedback control loop. That's the basis of a programming language I'm writing ^_^
- mk_stjames 2y agoThis is essentially the paradigm what Karpathy deemed to be "Software 2.0" in an article in 2017: https://karpathy.medium.com/software-2-0-a64152b37c35 https://karpathy.medium.com/software-2-0-a64152b37c35
- 2y ago
- tromp 2y ago> We should not accept this. If we don’t, then the future of computing will belong to biology, not logic. In this quote from Leslie Lamport, I took "If we don't" to mean "If we don't accept this". But the rest of the sentence made no sense then. Could it be a really awkward way to say: If we don't "not accept this", i.e. if we accept this?
- MBCook 2y agoI think you’re right, it means something like “if we don’t refuse to accept this”. That is rather awkward isn’t it. I really liked that whole block quote though.
- yencabulator 2y agoMaybe an earlier draft said "We should reject this. If we don't [...]", and was edited to be less harsh.
- justin66 2y agoI believe it was probably a typo, and one that existed in the original paper. The tricky thing about it is, a person might not notice it until it was pointed out. (I didn't - but I verified afterward that it's in Lamport's paper)
- ctenb 2y agoI just realized that the word for organ the music instrument and the body part is one and the same in English. (In dutch they're called orgel and orgaan respectively.) Which of these meanings is being referred to in the article? To me both could make sense.
- tomesco 2y agoThe definition of organ in this article is closest to the body part definition. The use of organ here relies on a less common definition: roughly a constituent part of some larger whole that performs a specific function.
- MBCook 2y agoI think that’s a great summary. As a native English speaker, it was understandable but feels rather foreign because you never hear parts of computers referred to that way these days.
- shiroiushi 2y agoNot just a specific function, but a necessary function. Usually, without an organ, the organism won't survive. So your fingers aren't organs, because you can survive (with some difficulty) without them, but without your stomach or heart or skin, you'll die.
- deleted 2y ago[deleted]
- bloody_bocker 2y ago> When people who can’t think logically design large systems, those systems become incomprehensible. And we start thinking of them as biological systems. And since biological systems are too complex to understand, it seems perfectly natural that computer programs should be too complex to understand. For some time I've been drawing parallels between ML/AI and how biology "solves problems" - evolution. And I also am bit disappointed by the fact the future might lead us in a different direction than mathematical elegance of solving problems.
- l33tbro 2y agoAre you able to share what these parallels are that you've drawn? I've always thought them to be slightly different processes.
- bloody_bocker 2y agoEvolution: optimization done by selection, result is the DNA, that does amazing (we can't match that with traditional programming) things but it's bloody hard to decipher. Neural network: created via training, does amazing things but (this is the area my knowledge is too small) it's bloody hard to decipher why is it doing the thing it does. "Traditional" programming: you can (as in article) explain it down to the single most basic unit.
- MBCook 2y agoI really loved that quote in the article. It’s such an excellent description of the “computer voodoo“ users come up with to explain what is, to them, unexplainable about computers. You’re right though, we’re basically there with AI/ML aren’t we. I mean I guess we know why it does the things it does in general, but the specific “reasoning“ on any single question is pretty much unanswerable.
- userbinator 2y agoThe main topic for this blog is a paper that describes what is now more commonly known as "von Neumann Architecture". This architecture is used in almost every computing device on earth I'd argue that MCUs, the highest volume of which are largely based on Harvard architecture, far outnumber von Neumanns.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- drcwpl 2y agoThere is a terrific interview with Tracy Kidder and Tom West from the Computer Museum https://ed-thelen.org/comp-hist/TCMR-V04.pdf https://ed-thelen.org/comp-hist/TCMR-V04.pdf
- jecel 2y ago"The terminology of calling computer parts "organs" is gone now, but the "Control" here describes what we now commonly refer to as CPU." Actually, what was described is currently called the "Control Unit". We divide CPUs into a Datapath (which includes registers, busses, ALU...) and a Control Unit which is either hardwired or microcoded. Decoding instructions is the job of the Control Unit though it might get a little help from the Datapath in some designs. The block diagram for a modern processor at the end of the article is just the Datapath - the Control Unit is not shown at all which is the most popular current style. It must actually exist in the chip and HDL sources, of course, if the processor is to actually do anything.