The reason things are moving fast here is that this notion of packaging multi-processors into a single CPU chip has started to revolutionize the way to support them.  Before this, each CPU was a separate processor with its own socket/slot which took lots of motherboard space and produced more heat, requiring more cooling.  Also, due to the proximity and more direct connections, they can 'talk' to each other much more quickly.  So, this single CPU multi-processor package is a good idea.

Don't know where some of you have been, but multi-processor computers have been around for a long time.  Check this Unisys link.  The first Cray multi-processor supercomputer was introduced in 1982.  Now, desktop multi-processing is somewhat new, but it has also been around since the early or mid 90's.  My Dual Xeon is already four years old and right next to it is an even older Dual P3 running my server.

As noted, the problem is software support.  For some time, there was no OS support (except for maybe Linuxish OSs).  Windows NT was the first, I think.  And now MacOSX of course.  Software developers need to specifically handle code being sent to multiprocessors so as to ascertain that interdependencies are carefully analyzed and handled (and minimalized as much as possible).  Code can't just be sent to any processor arbitrarily.  Therefore, it is no small feat and usually reserved for situations where the data/operations can be partitioned and run in parallel.

Never think 'old'.  I'll be 42 this year and still play metal, rock, blues, neo-classical on guitar and still do computer development.  I'm gettin' slower, but I'm not dead yet (MP&THG reference). ;)

Robert

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone