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 : Advanced Micro Devices - Moderated (AMD)
AMD 252.04+0.3%Jan 27 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: graphicsguru who wrote (239515)8/29/2007 12:38:01 PM
From: TenchusatsuRead Replies (2) of 275872
 
GG, > Now we know why CSI is taking so long. This unwinding mechanism sounds scary to me in its complexity. It's a big risk. On the other hand, Intel has done more complex things in the past, and gotten them to work. The P4 replay mechanism, for example. I find it impressive that there were no fdiv-like recalls on it.

I'm not 100% sure about what this "unwinding mechanism" is, but if it refers to cacheline conflicts, I know why it's complex. Basically, Intel intends to make CSI scalable beyond four sockets.

Too bad even four socket servers are declining thanks to multi-core.

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