SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Intel Corporation (INTC)
INTC 35.10+2.3%3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Tenchusatsu who wrote (107880)8/21/2000 12:58:51 PM
From: Scumbria  Read Replies (1) of 186894
 
Ten,

1) You only need to implement half as many execution pipes.

An execute pipe includes fetch, decode, dispatch, operand recovery, arithmetic operations, writeback and completion. In Willy, these stages are broken down even further. A fast ALU may reduce the need for a small amount of hardware, but I doubt it. The reason being that at 3.0GHz, data can only be forwarded a very small distance. Forwarding will probably be limited to the same pipeline.

2) Certain data hazards can be bypassed. If there is an instruction that depends on the results of the previous instruction, both can be sent down the double-speed ALU and be executed in one (regular) clock cycle. Two execution units running at normal speed will need two clock cycles to handle those instructions (thereby leaving one unit unutilized).

This is the big question about the Willy ALU. When does it actually remove bubbles from the pipeline? One obvious case is on pipeline refill, but it is not clear under what other circumstances it can provide this performance enhancement.

Scumbria
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext