The reason they are called cores and not processors is because they must share resources with the other cores (cache, bus etc) and that limits there effectiveness.
Didn't I just disprove that with the "dual-processor" Power Macintosh 9600 example? Also, there are lots of computers in the past that shared their busses with other things (the Mac LC, the Power Macintosh 5200, my old Compaq Presario) and plenty of systems that didn't even have cache. Since when is cache part of the definition of what a processor is?
EDIT: In case you didn't see that - the "dual processor" Power Macintosh 9500 and 9600 systems each had two PowerPC 604 processors soldered onto a single board that shared the same single bus, and a single, external L2 cache.
Besides, there were other "multi processor" systems from various manufacturers before all this "core" nonsense - I'm sure there are other examples of a similar setup.
i'm not gonna comment on this because i know dpaanlka is all over this now (
add: and i was right )
You know me well!
now to dpaanlka, how would you differentiate then, between 2 core on same chip and 2 core on 2 chips?
I would say a single chip with two cores/processors should be identified as a "Dual-Processor System," or "Dual-Core Chip," or something like that... but saying a single "processor" has two "cores" would be an oxymoron or whatever the term is.
"CPU" stands for "Central Processing Unit", does it not? It is
not (but often misused as) an acronym for "processor" - because "processing unit" does not specify how many processors are there.
So, "Dual Core CPU" would also be correct. But it still has two processors. The "unit" in CPU (coming from "unify") suggests that there could be even two or more individual processors/cores, working together in unity.