• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Integrated FSB for A64?!

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

jcw122

Member
Joined
Jun 25, 2004
OK im getting an A64 and i just learned that since the FSB is integrated into the A64s...this basicly means there isnt such thing as FSB for them. OK so if the freq. of an A64 is say 2.2ghz...then how do u get that number is there is no FSB to multiply the multiplier by? Id really appreciate it if someone could clear this up for me. Im a lil confused on this and slightly worried.
 
Basically, the integrated fsb removes the bottleneck from the memory controller, to the cpu, as well as many other high speed components. Hence the name HyperTransport is quite appropriate, and the chipset deals mostly with the pci bus. I think...
 
http://www.ocforums.com/showthread.php?t=306418

Intro to A64 Architecture

Traditionally, a Northbridge exists between the memory bus and the CPU. The rate at which data is transferred between the memory and CPU is known as the front side bus. However, the Athlon64’s memory controller is on-die, and as such, has no Northbridge, nor a front side bus. The Athlon64’s have two independent buses; one between the memory and the on-die controller, and another bus that communicates with the other system devices- the HyperTransport bus. The CPU’s clock speed is determined by the HyperTransport speed multiplied by a clock multiplier, which is why it’s often suggested to view the HyperTransport bus as if it were the front side bus. However, this is about where the similarities between the two diverge. Traditionally, the memory speed is derived off of the front side bus, and can be manipulated by FSB/memory ratios. In contrast, in the A64, memory speed is derived off of the CPU speed in CPU/memory ratios. This is why it’s rather inaccurate to say that the memory is ever running “synchronously.” The memory is always running asynchronously with respect to the CPU speed, off of which it’s derived. How fast it’s running with respect to the HyperTransport bus does not matter at all. There is no latency hit in running the memory slower than the HyperTransport bus. The HyperTransport bus’ effective speed is determined by an LDT(Lighting data transport) multiplier. While the front side bus could’ve been traditionally double or quad-pumped, the HyperTransport’s effective data rate can be anywhere from 1x to 5x it’s speed on the CPU.
 
Back