A partial benefit is to program in a language capable of addressing
disparate core processors in such a way that "the one hand washing the
other" is within means other than what is accorded the pseudo-
actuality of notoriety to programming as it's spoken. Forgive me.
Allow me to rephrase that into words that make sense. Time Magazine,
I happened to notice this week, says that Microsoft's Halo debut is
"beautiful." Beautiful obviously is within a means the program is
coded, written for matrixes timed to address both GPU/MPU cores over a
syncopated return we perceive in similar fashion for a cat rolling in
catnip. In actuality, programming over multiple cores is no different
in that modal forms predicating a logic behind that language is very
much abstract and without the determinism of established precepts
involving singe-core linearity. Perhaps, but an aspect to incongruity,
a stipend, portioned to residuals, as it were, much as would be a
practical implication of expectation from serious chess players if
asked to sit before a three-tiered board of 3D chess. Computer
science does have that tendency -- to flow slowly behind the
advancement of conditional relationships as presented and fashioned
for social determinacy. Whether you would use four more cores more
efficiently than your present four (on W7 - XP is limited to
two). . .I should doubt that without special considerations first on
the user's part to stage a semi-convoluted sequence of programs to
such end. Beyond what most would be likely conceive if capable of
implementing, and certainly beyond a return on benchmarks for present
means as averages to benefit overall processor power available and
utilized. It's rather a brutish approach, then, as affordable and
more cores impose themselves over all other considerations to approach
what practical limits no doubt would exist.