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) -- Ignore unavailable to you. Want to Upgrade?


To: pgerassi who wrote (199794)6/1/2006 12:04:34 PM
From: Joe NYCRead Replies (1) | Respond to of 275872
 
pete,

But that is also the plight of memory channels, they cannot both receive and transmit 12.8GB/s. They only go one way at a time. And then there is the overhead in both types of links. Memory typically has more overhead than HT.

Yeah, that's a good point, but you are being deliberately obtuse about this, while you know better.

A read access of one processor (or a graphics card, which was the subject of a discussion) and while the processor where memory resides is able to read memory at 12.8 GB/s (effective a little less), the requesting device can only receive 4 GB/s under 1 GHz HT 2.0, or 10.4 GB/s under HT 3.0. This limitation is the most glaring with integrated video solutions available on the market shortly, which will be limited to 4 GB/s of 12.8 GB/s. I don't thinks there is a question of the performance impact her.

that standard 16/16 HT link can be made asymmetric like 24/8 which would increase say read BW to 15.6GB/s, but lower write BW to 5.2GB/s.

That sounds like a great idea, especially for integrated graphics.

5.2GB/s is quite a bit faster than the current HT 2.0 16/16 link at 2MT/s of 4GB/s down. I don't know however if the HT 3.0 version allows dynamic link width changes. It would likely require 4-5 additional pins, but would allow the link to go to 30/2 for 19.5GB/s/1.3GB/s BWs. That would accommodate most low end GPUs.

I was wondering about the dynamic link width changes, and it appears it is not supported in current version. At least not in a way you and I would like it, that is a direction of links could reverse based on the amount of traffic that goes in either direction. I think as HT 3.0 is defined, it is defined at boot time.

BTW, there is a dynamic power management defined in HT 3.0, when some pins can go dark when there is no demand.

Lets face it, 2D work just isn't that BW intensive which is used for most GUIs. Even 2048x1536x32 uses only 12MB per frame. A 1.3GB/s link can easily accommodate over 100FPS which is higher than most refresh rates. 4GB/s can do 330FPS. With modest amounts of cache, low end 3D GPUs don't use that much memory BW. For any medium or high end GPU, it would use local memory anyway. Even if it was plugged into an AM2 socket, 12.8GB/s would be the equivalent of 256 bit wide memory at 400MHz. And that "local" memory could be used by the CPU in the other socket.

Except, in Vista, the UI is getting to be 3D-like. You also need ability to decode HD signal at good quality for a mainstream graphics of the near future.

Personally though I would agree that 2 HT 16/16 links should be the minimum for any enthusiast CPU socket(s). The additional pins used for separate DDR(2) address and command pins should only needed to remove one HT 16/16 link and not two from the socket 940 to 939 transition. There should be enough room in AM2 to accommodate one additional HT 16/16 link.

It looks like AM2 does support 2 HT links. I hope more details will emerge today.

Joe