lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2406302009480.43454@angie.orcam.me.uk>
Date: Tue, 2 Jul 2024 00:48:00 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Arnd Bergmann <arnd@...db.de>, "Paul E. McKenney" <paulmck@...nel.org>, 
    John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>, 
    Arnd Bergmann <arnd@...nel.org>, linux-alpha@...r.kernel.org, 
    Richard Henderson <richard.henderson@...aro.org>, 
    Ivan Kokshaysky <ink@...assic.park.msu.ru>, 
    Matt Turner <mattst88@...il.com>, Alexander Viro <viro@...iv.linux.org.uk>, 
    Marc Zyngier <maz@...nel.org>, linux-kernel@...r.kernel.org, 
    Michael Cree <mcree@...on.net.nz>, Frank Scheiner <frank.scheiner@....de>
Subject: Re: [PATCH 00/14] alpha: cleanups for 6.10

On Fri, 31 May 2024, Linus Torvalds wrote:

> The fact is, the original alpha is the worst architecture ever made.
> The lack of byte instructions and the absolutely horrendous memory
> ordering are fatal flaws. And while the memory ordering arguably had
> excuses for it ("they didn't know better"), the lack of byte ops was
> wilful misdesign that the designers were proud of, and made a central
> tenet of their mess.
> 
> And I say that as somebody who *loved* it originally. Yes, the lack of
> byte operations always was a pain, because it really caused the IO
> subsystem to be a nightmare, but I was young, I was stupid, it was
> interesting, and I had bought into the kool aid.

 Looking from today's perspective it was clearly a bad choice.  However it 
was 30+ years ago, it wasn't so certain as it is now that x86 was there to 
stay -- indeed as I recall it DEC had the ambition to phase x86 out with 
their Alpha (whether they approached it the right way business-wise is 
another matter) -- so the notion of having a fully byte-addressed machine 
perhaps wasn't yet so obvious to DEC engineers as it is now, when most if 
not all the current CPU architectures have these fundamentals the same.  

 As I say it may have been the final attempt to do something differently 
before x86 domination forced everyone to be at least remotely compatible.

 And there used to be weirder architectures before people moved away from 
them and settled on the current paradigm, just as nobody wants to build a 
general-purpose atmospheric railway anymore and yet a while ago not only 
it didn't appear ridiculous, but such stuff was actually built and run, 
such as the South Devon Railway.

 And then it wasn't the only failed attempt: remember the i860 or the 
iAPX432?  At least the Alphas weren't a total disaster, they made their 
impact, the worst mistakes have been fixed as the architecture evolved, 
and the engineering legacy remains, often in unexpected places.

  Maciej

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ