Re: A possible way...
That's exactly my guess. If you can ***ign sub units by speed to reduce power, there's no reason NOT to use it for splitting the data path.
Effectively IBM has built a 2 core, bridgeable, on-the-fly throttleable paired 32 bit G3 at half the power consumption of G4 and a 256 bit wide L1 cache that can also be ***igned in chunks on the fly.
(pant, pant......What a mouthful!)
Indications are that G5 is more multi-processor friendly, so 4 two-on-one-chip, Ghz, bridgeable G3's. That's SICK. Stick that on a 200Mhz bus with 4 Gigs and Itanium looks like a toy.
Originally posted by Catfish_Man
A 64 bit chip would.... work like Altivec and accept 2 32 bit words at a time. It would require programs to be written to take advantage of it, but it would basically be like a mini-Altivec for non vector operations. If the program didn't have the type of operations that use SIMD then it would give any improvement.
That's exactly my guess. If you can ***ign sub units by speed to reduce power, there's no reason NOT to use it for splitting the data path.
Effectively IBM has built a 2 core, bridgeable, on-the-fly throttleable paired 32 bit G3 at half the power consumption of G4 and a 256 bit wide L1 cache that can also be ***igned in chunks on the fly.
(pant, pant......What a mouthful!)
Indications are that G5 is more multi-processor friendly, so 4 two-on-one-chip, Ghz, bridgeable G3's. That's SICK. Stick that on a 200Mhz bus with 4 Gigs and Itanium looks like a toy.