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 236.78-6.1%Jan 30 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: combjelly who wrote (79798)5/8/2002 9:28:07 PM
From: fyodor_Read Replies (1) of 275872
 
combjelly: HTT used as a memory interface would have the problem that it would be inherently shallow, i.e. it's point to point. But there wouldn't be the propagation delays because of this either. It would also have the nice property that as you add memory, your bandwidth goes up. It's downside is that your memory expansion is limited by the number of HTT ports, so for very large memory arrays, you would need to have HTT switches that would add some to the latency.

You can also daisy-chain using HyperTransport. I assume this is what he was referring to.

Unless you are talking a fixed memory situation (i.e. a closed box like a console), daisy-chaining would be the only feasible solution. It just wouldn't make sense to lay down separate traces to all memory banks when 90% aren't going to use them.

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