[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2407040044180.38148@angie.orcam.me.uk>
Date: Thu, 4 Jul 2024 23:21:34 +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 Tue, 2 Jul 2024, Linus Torvalds wrote:
> > Precisely my point! We got so used to think in multiples of 8 bits that
> > other approaches seem ridiculous.
>
> But Maciej - alpha *was* designed for bytes. It wasn't a Cray 1. It
> wasn't a PDP-10. It was designed by the time people knew that bytes
> were the dominant thing, and that bytes were important and the main
> use case.
>
> But it was designed BADLY. The architecture sucked.
OK, perhaps it was those people who decided to make it that way that
lived in a parallel universe.
> Give it up. If alpha had been designed in the 60s or 70s when the
> whole issue of bytes were was debatable, it would have been
> incredible.
>
> But no. It was designed for byte accesses, and it FAILED AT THEM.
I guess they decided that trading byte and word accesses for simpler bus
logic that does not have all the bits required to issue an RMW operation
to recalculate the ECC syndrome on such accesses was a good deal, and I
guess they did not realise data race implications or thought they could be
sorted in a reasonable way. The avoidance of RMWs is explicitly mentioned
in the preface to the Alpha ARM.
And I guess you are aware that getting an asynchronous multi-bit ECC
error interrupt for a partial write the origin of which has long gone and
all you have is the physical address is also a horror to handle.
Bad choice I guess anyway. Too many guesses I guess too.
Maciej
Powered by blists - more mailing lists