🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.arch
Article #20601

Re: RISC as a "technology window"?

#20601
From: Jonathan Levy
Date: Fri, 31 Mar 1989 20:25
35 lines
2605 bytes
In article <6417@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
>In article <13404@steinmetz.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes:
>>  There will continue to be a demand for processors with a very high
>>instruction rate (call them RISC if you will), and also for processors
>>which will perform a given task faster with limited memory bandwidth.
>
>	Quite true.  Not everyone designs workstations bought solely by
>larger corporations.  There is _signifigant_ demand for CPUs that are
>a) fairly cheap - say current '030/881 (16MHz) pricing, and b) do the
>most _work_ given a specific memory bandwidth, determined by the speed of
>jelly-bean memory parts - say 100-120ns currently, and without expensive
>external caches.
>
>	You could sell a lot of CPUs like that.

Funny you should mention that. National Semiconductor has just announced
a new processor for the Embedded market. This is the NS32GX32.
It has the NS32532 pipeline core and the same performance 
(18,335 d/s, 8 to 10 vax mips average at 30 MHZ).
The processor is *cheap* both in actual chip cost (for pricing you will need
to contact marketing...), and what is more important, in system cost.

System cost is minimized by providing the system a very simple 
interface (non multiplexed address and data bus, one of each), 
a harvard architecture which is *ON* chip (why burden the designer
with our problems), two on-chip caches (1K data cache, 0.5K instruction cache),
code density which is second to none, dynamic bus sizing for peripherals
and boot ROMs, long address to ready timing, long address to data timing, etc.
All this provides for a CPU which is very insensitive to wait states. 
We have a system which was designed with a single bank of DRAM (no interleave)
which provides the CPU with 2 wait states on the first access, and one
wait state on burst accesses. The performance of this system is more than
85% of the maximum! One cannot do that with a generic RISC.

Jonathan
Technical Details
Message-ID: <10262@nsc.nsc.com>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!bloom-beacon!apple!amdahl!nsc!levy
References: <1552@vicom.COM> <15690@cup.portal.com> <1562@vicom.COM> <15702@clover.ICO.ISC.COM> <27681@apple.Apple.COM> <15695@winchester.mips.COM> <22974@ames.arc.nasa.gov> <13404@steinmetz.ge.com> <6417@cbmvax.UUCP>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!bloom-beacon!apple!amdahl!nsc!levy
From: levy@nsc.nsc.com (Jonathan Levy)
Newsgroups: comp.arch
Subject: Re: RISC as a "technology window"?
Message-ID: <10262@nsc.nsc.com>
Date: 31 Mar 89 20:25:21 GMT
References: <1552@vicom.COM> <15690@cup.portal.com> <1562@vicom.COM> <15702@clover.ICO.ISC.COM> <27681@apple.Apple.COM> <15695@winchester.mips.COM> <22974@ames.arc.nasa.gov> <13404@steinmetz.ge.com> <6417@cbmvax.UUCP>
Reply-To: levy@nsc.nsc.com.UUCP (Jonathan Levy)
Organization: /usr/lib/news/organization
Lines: 35