Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Politics : Formerly About Advanced Micro Devices -- Ignore unavailable to you. Want to Upgrade?

To: Scumbria who wrote (91855)	2/6/2000 8:10:00 PM
From: tejek	Respond to of 1576160

I know that I am belaboring the issue but I want to have one more go around. 1. The amount of work required to execute an instruction is the same, regardless of the length of the pipeline. And there are the same number of instructions no matter the length of the pipeline? BTW an instruction is a specification, right? 2. It is more difficult to architect a deep pipeline. It requires more thought up front to partition the pipe. Got it, I think....the additional architectural thought upfront reduces the work load in production? 3. It is easier to design each stage of a deep pipeline. Because the amount of work done by a short stage is reduced, the design complexity is also reduced. Referring to point 2, that would mean that there is more partitioning and therefore ther are more short stages to a deep pipeline than an existing pipeline, right? Scumbria, thanks for your patience. ted