🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.arch
Article #2416

Re: Pipeline Interlock

#2416
From: chiba
Date: Tue, 03 Oct 1989 04:22
51 lines
2271 bytes
In article <15904@dartvax.Dartmouth.EDU> jskuskin@eleazar.dartmouth.edu (Jeffrey Kuskin) writes:
>
>So...my question:  most (all?) of the current RISC processors
>(29000, 88000, 80860, etc) include pipeline interlock logic.

  MIPSco and SPARC also

At Hot Chips, John M. mentioned interlocks as one of the nice features
of the MIPSco chips.

>Could someone familiar with these processors comment on the
>implications of this decision:
>
>    -- How much of the total chip area is occupied by
>       pipeline interlock logic?

Not much. 

>
>    -- If the interlock logic were eliminated, could the 
>       processor cycle time be decreased?  By how much?

In general, very little if at all. My drinking buddies who are hw
jocks think they know how to do such things in parallel with real
work. :>
> 
>    -- How long (in person-weeks/years, whatever) did it take
>       to design the interlock logic?  

Dunno. Certainly seems unlikely to anywhere near as costly as the
software havoc not having interlocks costs. Aside from the compiler
development, inevitable bugs introduced by hand coders and the like,
is the fact that your binaries simply won't run on the next generation
device (unless you really constrain the hw jocks). 

Upgrading your machine --> all new software is unpopular. Sufficiently
so that it seems that few if any commerical designs will completely
skip interlocks.

>
>
> 
>   **  Jeff Kuskin,  Dartmouth College
> 
>   **  E-Mail:  jskuskin@eleazar.dartmouth.edu


Keith H. Bierman    |*My thoughts are my own. !! kbierman@sun.com
It's Not My Fault   |	MTS --Only my work belongs to Sun* 
I Voted for Bill &  | Advanced Languages/Floating Point Group            
Opus                | "When the going gets Weird .. the Weird turn PRO"
Technical Details
Message-ID: <125664@sun.Eng.Sun.COM>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!sun-barr!newstop!sun!chiba!khb
References: <15904@dartvax.Dartmouth.EDU>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!sun-barr!newstop!sun!chiba!khb
From: khb%chiba@Sun.COM (chiba)
Newsgroups: comp.arch
Subject: Re: Pipeline Interlock
Message-ID: <125664@sun.Eng.Sun.COM>
Date: 3 Oct 89 04:22:10 GMT
References: <15904@dartvax.Dartmouth.EDU>
Sender: news@sun.Eng.Sun.COM
Reply-To: khb@sun.UUCP (chiba)
Distribution: na
Organization: Sun Microsystems, Mountain View
Lines: 51