Path: Xl.tags.giganews.com!local-1.nntp.ord.giganews.com!nntp.supernews.com!news.supernews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 28 Apr 2024 02:54:48 +0000
From: John Larkin <jjSNIPlarkin@highNONOlandtechnology.com>
Newsgroups: sci.electronics.design
Subject: Re: Anticipating processor architectural evolution
Date: Sat, 27 Apr 2024 19:52:55 -0700
Organization: Highland Tech
Reply-To: xx@yy.com
Message-ID: <j4er2j5lsole1pb5ekp79rqspf67j7qc86@4ax.com>
References: <v0k0ng$kiku$1@dont-email.me>
X-Newsreader: Forte Agent 3.1/32.783
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 35
X-Trace: sv3-wjBW9OesNM4T3ZxLID3U5l9cVYxUr47i5uJqTXwGcnk3xyDx+yYbnGRdHGVDfyAOUrQhDiz0qkhymCO!Xc7wD4W4jCK4NWoAtOBcMsXisd/m9gMQGKMpBzga1QGmVsCa9DpKvUXP8XEMRmwk9fJ/8OQgXCkX!DR0dVA==
X-Complaints-To: www.supernews.com/docs/abuse.html
X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 2488

On Sat, 27 Apr 2024 16:11:30 -0700, Don Y
<blockedofcourse@foo.invalid> wrote:

>I've had to refactor my RTOS design to accommodate the likelihood of SMT
>in future architectures.
>
>Thinking (hoping?) these logical cores to be the "closest to the code",
>I call them "Processors" (hysterical raisins).  Implicit in SMT is the
>notion that they are architecturally similar/identical.
>
>These are part of PHYSICAL cores -- that I appropriately call "Cores".
>
>These Cores are part of "Hosts" (ick; term begs for clarity!)... what
>one would casually call "chips"/CPUs.  Note that a host can house dissimilar
>Cores (e.g., big.LITTLE).
>
>Two or more hosts can be present on a "Node" (the smallest unit intended to
>be added to or removed from a "System").  Again, they can be dissimilar
>(think CPU/GPU).
>
>I believe this covers the composition/hierarchy of any (near) future
>system architectures.  And, places the minimum constraints on said.
>
>Are there any other significant developments in the pipeline that
>could alter my conception of future hardware designs?

Why not hundreds of CPUs on a chip, each assigned to one function,
with absolute hardware protection? They need not be identical, because
many would be assigned to simple functions.

The mess we have now is the legacy of thinking about a CPU as some
precious resource.