CheesePoofs
Diamond Member
- Dec 5, 2004
- 3,163
- 0
- 0
Originally posted by: Brian23
Originally posted by: CheesePoofs
Originally posted by: Brian23
Originally posted by: redhatlinux
Look, there is ALWAYS room for niche market company's, but did anybody here experience Cache on a STICK .... great idea bak in the day. CPU cache memory, looked very similar to main memory of today, "plugged" in to the mobo. Case vendor's even made a 'easliy removable panel', for those "not trained at opening their BOXES ... he he. I built a system for my bro-in-law. OOOPs, tried to upgrade it to larger cache... NOGO, the timing was that critical. HYPER-TRANSPORT is SOOOOOOO SLOW compared to CPU speeds, VERY fast for a BUS, useless for a CPU.
SLOCKETS, socket adapters have been around for ever.... I've been posting in this forum, under a different ID for ever ... find out why certain manuf SLOCKETS only worked with certain mob's .... TIMING, VOLTAGE,Noise EMI component quality, etc etc. No WAY JOSE.
Why are you telling me that Hyper-Transport is slow for a CPU? Did you know that the Athlon 64 exclusively uses Hypertransport to comunicate with the rest of the system? (minus the memory.) My suggestion of putting the core on a seprate plug in board would not effect the system speed because the hyper transport would still run at the same speed. There would be no technical differnces except that the high speed part of the motherboard (memory interface) would be designed, controlled, and manufactured by AMD. The main benefit is increased upgradability options and lower cost for motherboards.
I think redhatlinux is saying that hypertransport is slow for communication between different parts of the CPU (ie processing units and the cache) or between the CPU and the RAM.
If you're suggesting that the ram be on the card with the CPU, then there are no technical differences except that you have a connector in the middle of the hypertransport lane.
I think you're the first person who understands what I've been trying to say.![]()
