Re: architectural goals, Byte Addressability And Beyond

Liste des GroupesRevenir à c arch 
Sujet : Re: architectural goals, Byte Addressability And Beyond
De : already5chosen (at) *nospam* yahoo.com (Michael S)
Groupes : comp.arch
Date : 02. Jun 2024, 10:01:11
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240602120111.0000771e@yahoo.com>
References : 1 2 3 4 5
User-Agent : Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
On Fri, 31 May 2024 19:44:49 -0000 (UTC)
John Levine <johnl@taugh.com> wrote:

According to John Savard  <quadibloc@servername.invalid>:
On Thu, 30 May 2024 03:25:14 -0000 (UTC), John Levine
<johnl@taugh.com> wrote:
 
I do not entirely understand why IBM keeps adding special purpose
instructions to z. Maybe it's partly marketing, but they have a
largely captive audience so it has to be more than that. 
>
One possibility is to _keep_ that audience captive even after all the
patents expire that are applicable to machines with the
z/Architecture in its current state, if you are reluctant to believe
that these new instructions genuinely improve performance. 
 
Back in the last millenium there were a bunch of companies that made
clones of IBM mainframes. They all failed. It's the whole ecosystem of
hardware and software, not just individual features that keep the
customers nor patents.
 
I have to say I'm somewhat surprised that IBM has put a lot of effort
into running linux on zSeries, since that's about as un-captive as you
can get. I would imagine that for some kinds of heavily threaded
workloads they could be competitive since the z machines have upwards
of a hundred CPUs with a shared mostly consistent cache.
 

z15 appears to peak at 190/380 User-visible cores/threads.
That's less than quad-socket 56-core Intel Xeon. Quad-socket Xeons
are much less popular than they used to be 20 years ago, but
HP/Dell/Lenovo would still sell you one if you insist.
IBM's own Power System E980 can give you whooping 1536 threads in
maximal configuration.

May be, Telum pulls zArch ahead of those. I don't know much about it.



Date Sujet#  Auteur
31 May 24 * Re: architectural goals, Byte Addressability And Beyond42John Savard
31 May 24 `* Re: architectural goals, Byte Addressability And Beyond41John Levine
1 Jun 24  +* Re: architectural goals, Byte Addressability And Beyond31John Savard
1 Jun 24  i+* Re: architectural goals, Byte Addressability And Beyond20Thomas Koenig
2 Jun 24  ii+* Re: architectural goals, Byte Addressability And Beyond6John Savard
2 Jun 24  iii`* Re: architectural goals, Byte Addressability And Beyond5Thomas Koenig
2 Jun 24  iii +* Re: architectural goals, Byte Addressability And Beyond3John Levine
3 Jun 24  iii i`* Re: architectural goals, Byte Addressability And Beyond2OrangeFish
3 Jun 24  iii i `- Re: architectural goals, Byte Addressability And Beyond1John Levine
4 Jun 24  iii `- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro
4 Jun 24  ii`* Re: architectural goals, Byte Addressability And Beyond13Lawrence D'Oliveiro
5 Jun 24  ii `* Re: architectural goals, Byte Addressability And Beyond12Lawrence D'Oliveiro
5 Jun 24  ii  +- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro
6 Jun 24  ii  `* Re: architectural goals, Byte Addressability And Beyond10George Neuner
6 Jun 24  ii   +* Re: architectural goals, Byte Addressability And Beyond6John Levine
7 Jun 24  ii   i+* Re: architectural goals, Byte Addressability And Beyond4Lawrence D'Oliveiro
7 Jun 24  ii   ii`* Re: architectural goals, Byte Addressability And Beyond3Stephen Fuld
7 Jun 24  ii   ii `* Re: architectural goals, Byte Addressability And Beyond2Lawrence D'Oliveiro
7 Jun 24  ii   ii  `- Re: architectural goals, Byte Addressability And Beyond1Stephen Fuld
7 Jun 24  ii   i`- Re: architectural goals, Byte Addressability And Beyond1Terje Mathisen
6 Jun 24  ii   +- Re: architectural goals, Byte Addressability And Beyond1Lynn Wheeler
6 Jun 24  ii   +- Re: architectural goals, Byte Addressability And Beyond1OrangeFish
7 Jun 24  ii   `- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro
2 Jun 24  i`* Re: architectural goals, Byte Addressability And Beyond10John Dallman
2 Jun 24  i `* Re: architectural goals, Byte Addressability And Beyond9Thomas Koenig
2 Jun 24  i  `* Re: architectural goals, Byte Addressability And Beyond8John Dallman
3 Jun 24  i   `* Re: architectural goals, Byte Addressability And Beyond7Anton Ertl
3 Jun 24  i    `* Re: architectural goals, Byte Addressability And Beyond6John Dallman
3 Jun 24  i     `* Re: architectural goals, Byte Addressability And Beyond5Michael S
5 Jun 24  i      `* Re: architectural goals, Byte Addressability And Beyond4John Dallman
5 Jun 24  i       +- Re: architectural goals, Byte Addressability And Beyond1Michael S
5 Jun 24  i       `* Re: architectural goals, Byte Addressability And Beyond2Anton Ertl
5 Jun 24  i        `- Re: architectural goals, Byte Addressability And Beyond1MitchAlsup1
2 Jun 24  +- Re: architectural goals, Byte Addressability And Beyond1Michael S
2 Jun 24  +- Re: architectural goals, Byte Addressability And Beyond1John Dallman
4 Jun 24  `* Re: architectural goals, Byte Addressability And Beyond7Lawrence D'Oliveiro
4 Jun 24   +- Re: architectural goals, Byte Addressability And Beyond1John Levine
5 Jun 24   `* Re: architectural goals, Byte Addressability And Beyond5John Dallman
5 Jun 24    +- Re: architectural goals, Byte Addressability And Beyond1Michael S
6 Jun 24    `* Re: architectural goals, Byte Addressability And Beyond3Lawrence D'Oliveiro
6 Jun 24     `* Re: architectural goals, Byte Addressability And Beyond2MitchAlsup1
6 Jun 24      `- Re: architectural goals, Byte Addressability And Beyond1Lawrence D'Oliveiro

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal