Slashdot Log In
Intel Expands Core Concept for Chips
Posted by
CowboyNeal
on Sat Dec 18, 2004 09:31 AM
from the symmetrical-multithreading dept.
from the symmetrical-multithreading dept.
Aziabel writes "As most of you have probably heard, Intel plans to come out with chips containing two processing cores next year, but that's just the start. The Santa Clara, Calif.-based chip giant intends to exploit the concept of using multiple processor cores; chips with four cores and eight cores will eventually join dual-core chips, which will begin to appear from Intel next year. The company's research department is also looking at the feasibility of creating chips with hundreds of cores to assist servers and supercomputers with large numbers of relatively repetitive calculations, said Steve Smith, vice president of the desktop platforms group at Intel. The focus on multiple cores arises from Moore's Law, which dictates that the number of transistors on a chip doubles every two years. I say, the more the better. Keep 'em coming, chip-makers!"
This discussion has been archived.
No new comments can be posted.
Intel Expands Core Concept for Chips
|
Log In/Create an Account
| Top
| 222 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Can you imagine... (Score:2, Funny)
(http://www.ioerror.us/ | Last Journal: Sunday May 22 2005, @06:28AM)
Cell Processor (Score:5, Interesting)
(http://zzz.zggg.com/)
Re:Cell Processor (Score:5, Interesting)
(http://abrij.org/)
But we all know that nothing really changes until memory access changes. Memory continues to be the bottleneck, so if the only thing a processor with more cores can do fast is crunch numbers, you'd get more bang for the buck with better/more vector processing units.
Now, if/when they come out with memory that can be reorganized on-the-fly, perform large-scale simple massively-parrallel operations, and do some content-addressable tricks, that will be a signifigant development. I don't know how long it would take that to make it into higher level programming languages, though. It kinda of turns the job of writing programs on it's head.
Re:Cell Processor (Score:5, Informative)
(http://www.rabidpenguin.org/ | Last Journal: Wednesday August 22 2001, @09:13PM)
Re:Cell Processor (Score:4, Interesting)
>simple massively-parrallel operations, and do some content-addressable tricks, that will be a
>signifigant development. I don't know how long it would take that to make it into higher level
>programming languages, though. It kinda of turns the job of writing programs on it's head.
Have you ever stumbled on FPGAs ? It's already there. The problem is, as I see it, it does turn writing programs on it's head. Thus, very few people outside of the hardware design crowd know what to do with them.
Just think how many people do get exposed to digital design vs programming. How many people do go beyond a vague idea of a processor working on data sitting in memory ? How many CS graduates are utterly unhappy about digital design classes ?
I like (Score:1, Offtopic)
(Last Journal: Monday September 25 2006, @07:02PM)
Long-term strategy of this? (Score:5, Insightful)
Kind of like to what I suspect Microsoft has been trying to do against Lindows for a while now, namely complicate their API more and more. And with IE and HTML.
Of course they're well within their rights to try. We'll just build a better idiot savant. Or let Steve Jobs keep making Apples that no one can really imitate in the first place.
Re:Long-term strategy of this? (Score:5, Insightful)
Why should this have anything to do with the instruction set? The principle is exactly the same as for existing multi-processor systems, but on the same chip.
Have we hit a wall for computational ability? (Score:4, Interesting)
Great (Score:5, Funny)
Performance rateing (Score:5, Informative)
Read overclockers.com for some good speculation on what the good/bad/ugly features are likely to be.
Not that kind of law! (Score:5, Insightful)
(Last Journal: Saturday April 12 2003, @07:08AM)
The focus on multiple cores arises from Moore's Law, which dictates that the number of transistors on a chip doubles every two years.
I don't think non-compliance with Moore's Law is a felony. It's an observation, not a statute. Moore's Law arises from the fact that transistor counts keep doubling, not the other way around.
Also, doubling the number of transistors in any way possible doesn't necessarily translate into double the power for any given application. In this case, multiple cores are good news for multi-threaded or forking server apps, but rather less interesting for a lot of desktop apps. Intel obviously has a vested interest in pushing ever larger die sizes, because it does large dies better than anyone else. Whether this will always be in the interests of the rest of the industry, let alone the end user, is less obvious.
Re:Not that kind of law! (Score:5, Interesting)
hmm (Score:3, Interesting)
(http://www.fone-me.com/)
if not, how feasable is a multicore > single core emulation in linux.
Re:hmm (Score:4, Informative)
You see an OS runs multiple threads in the first place it just switches between them as each need run time.
But for given program to be written to use 2 or more threads (looks to the OS as 2 or more programs) takes work.
So take a program that is already written and place in a multi-core/processor/thread enviroment with all else being equal - it will run as fast as it did before.
What will run faster is all of it. Take two of these old programs and run them in the multi-core/processor/thread enviroment and they each take same processing time unto themself, but the obversied time is shorter because they are both actually running at SAME time.
Yeah, yeah. (Score:3, Insightful)
(http://gazonk.org/~eloj/ | Last Journal: Tuesday June 07 2005, @01:18PM)
>will begin to appear from Intel next year.
Very likely this is marketing sp33k for "will be paper-launched at the last day of next year"
HARD-core.. eh? (Score:2)
(Last Journal: Tuesday September 14 2004, @08:18PM)
8 cores, next year? i think not! (Score:1, Funny)
Officer of Law: you are under arrest for breaking the Moores Law, that allows you only double the number of transistors within a year.
Yet again Intel pretends to invent a technology (Score:4, Insightful)
http://www.theregister.co.uk/2004/11/26/ibm_power
It reminds me of the way that Intel pretended that they invented integrated wireless technology with its Centrino chip only after Apple had been shipping laptops for nearly two years with internal wireless cards.
Normally, asking if they had no shame would be appropriate but it is unfortunately clear (without the need to ask) that they don't.
Dual cores for Intel next year? (Score:4, Interesting)
(http://slashdot.org/)
AMD has said that dual cores will be clocked anywhere from 600Mhz to 1Ghz slower than the single core counterpart, namely because of heat issues. There are many more issues that arise with dual cores here are a few
Cache correnance
Bus contention
software implementation
plus more
It will be interesting none the less on how each manufactorer overcomes the issues with multi-core chips and the benefits to the user of of multi-core.
Re:Dual cores for Intel next year? (Score:4, Informative)
In AMD SMP systems, each CPU has its own separate link to RAM and peripherals. Each CPU also has a link to each other CPU. If CPU A needs something in CPU B's cache, it just asks CPU A to send it that data across the inter-CPU link.
As you add CPUs in an Opteron server, you actually increase the RAM/system bandwidth. Compare that to a Xeon system where adding CPUs reduces the bandwidth available to each CPU (system/RAM bandwidth is constant).
There's a beautiful set of articles over at Ars Technica describing the SMP abilities of the Athoon, the Opteron, and the Xeon. It's amazing Intel has been able to sell any 8-way systems.
OOH object oriented hardware (Score:2, Interesting)
(http://sourcery.blogspot.com/ | Last Journal: Monday March 27 2006, @12:54AM)
The basic idea is that a computer could comprise many, many tiny CPUs, each with its own tiny local memory.
A given (CPU+RAM) could be designated to operate as RAM for another CPU, so the MMU/OS could balance the number of processes needing memory with those needing processors.
A (CPU+RAM) could also be labeled as a slave to others, so a multithreaded application could have the number of processors it needed.
I haven't thought about it in a while, and it's been some time since I studied architecture, so probably these ideas are hopelessly naive.
So, how do ... (Score:1)
Wafer computing at last? (Score:2)
When manufactufing chips, they're done so in wafers. Then the wafer is cut up into its component parts, and each part is sealed in its own case. It would seem to be more efficient to just stick the whole damn wafer in a single case.
It would give a whole new meaning to "pizza box server", as the wafer and case would closely match the size of a pizza and box, respectively.
Sun has 8 Way Already (Score:2)
(http://www.freesql.org/)
Yes they do (Score:4, Informative)
If you want to know a bit more about it, I wrote it up a few weeks ago here:
http://www.theinquirer.net/?article=19423
-Charlie
Sun already ships this (Score:2, Informative)
(http://slashdot.org/)
-1 Troll (Score:1, Troll)
(http://www.cyberista.com/)
WTF?
Intel is not doing all that well in the core races (Score:5, Informative)
http://www.theinquirer.net/?article=20270
h
Needless to say, their long term strategies are a tad up in the air right now.
As for their desktop (IE P4 based) dual core plans, there are 2 generations planned. The first is a simple pairing of 2 current cores with a minimum of tweaks, basically a scared response to AMD. The second one is really the first one they planned, and it is a lot more sophisticated.
AMD was there from long before Day One, and have the most coherent philosophy on dual cores for the desktop/server.
Rather than re-write all my own articles here, here is a link where I break down all of Intel's dual core plans as well as some of AMDs.
http://www.theinquirer.net/?article=17906
Sorry for all the self links, but I don't really want to keep re-writing that stuff, links are the reason behind the web, right?
-Charlie
GNU Hurd (Score:1)
Will this hardware development bring quantum computing [wikipedia.org] any closer to reality?
More and more cores.. less and less bandwidth (Score:4, Insightful)
(http://www.lingula.org.uk/)
Remember that each of these processing cores will have to share their memory bandwidth and possibly level 2 cache as well. As it is Intel's EM64T Xeon processors really feel the bandwidth bottleneck in their memory interface and can easily saturate it.
I can see a dual core Xeon being able to saturate its memory bus on its own. Similarly, the dual core Opteron, unlike a dual processor Opteron, will have to share a single memory bus and hence be slower than a dual processor machine.
Adding extra cores merely moves the computing bottleneck elsewhere, it's not a panacea.
Not a problem (Score:4, Interesting)
Niagara (see my post above) is bandwidth rich, the AMD solutions are also. The only ones with a looming problem are Intel until CSI comes on in a few years, but that is manageable.
Moral, Sun OK, AMD OK, Intel solid plan.
-Charlie
Yer Laws (Score:4, Interesting)
(http://slashdot.org/~Doc%20Ruby/journal | Last Journal: Thursday March 31 2005, @01:48PM)
Engineers especially must understand that "laws" of nature, including human innovation, are governed by an "invisible hand". Not some imaginary deity, or some government, or some mythic genius. Rather, there is a deeper order to events, like the way every triangle has 180 degrees, the Sun "comes up" every morning, controversial Slashdot posts will get mod'ded "Troll", without any false statements or duplicity. We're engineers: our job is to engage the deeper order, understand it, model it, and exploit it, without further mystifying it.
Tera's MTA did this years ago (Score:2)
The MTA was a commercial failure. Tera's inability to execute as a company was a major reason.
It is fun to watch Intel chase AMD.
This is nothing new. (Score:1)
(Last Journal: Thursday October 17 2002, @10:28AM)
Besides, putting a math coprocessor alongside every integer unit was the beginning of multi-core CPUs.
I wanna see (Score:1)
That would be, like, totally awesome. You could play Doom3 and Half Life 2 at high quality.
However, you could also convert the screener of "Doom" into xvid/mp3 within a few minutes. Which means it's available faster, which means there will be more niave bastards downloading the thing. Which means more psychiatric evaulations, and more medicine.
*invests in Pfiser, GlaxoSmithKline, and Merck*
all bow to moore (Score:1)
yeah its because of moore's law. you are such a frigging idiot.
Intel playing follow the leader? (Score:1)
Why wait? AMD has this now and it appears Intel is now following AMD in this direction.
AMD Press Release [amd.com]
Shouldn't that be... (Score:2)
Shouldn't that be, the Moore, the better?
Will this affect software licensing costs? How? (Score:1)
(http://slashdot.org/~davidwr/journal/ | Last Journal: Friday November 09, @09:19PM)
But what exactly IS a CPU from a software-licensing perspective?
I anticipate a few court cases over this, particularly involving small- and medium-sized software vendors and anyone selling high-dollar software.
Big players selling sub-$500/cpu software will hopefully be more interested in goodwill than greed and will offer the market reasonable pricing for these not-quite-multi-cpu computers.
Hitting the wall (Score:2)
Core Limit (Score:2)
All I want to know is ... (Score:2)
Bring on the software bugs (Score:1)
Misquoting Moore's law (Score:2)
Multi-core/processor programming automatically (Score:4, Insightful)
Functional programmming languages examples are Lisp and OCaml.
Oh, correction, from a previous
OTOH, it is theoretically possible to automatically multithread purely functional programs, especially if they're lazy like Haskell. So it could end up being a very important language on multi-processor and distributed systems.
The only way I see multi-core processors or cluster-like processors (Cell) succeed is if programmers switch to languages like that. Any other way would introduce too many bugs in programs. Computers should make life easier, not harder. Even for programmers.
Eventually, multi-core/processor is the only way forward, long before single-processors have to heat up to supernova temperatures to increase speed.
We're just at the beginning of computing. Looking back, programmers of the future will pity us poor folk who had to make do with only 1 CPU. However, we need the right tools to move forward. Anyone know if there's an automatically multithreading (functional) programming language in existance or being invented?
Tying the cores together? (Score:2)
(http://slashdot.org/)
-d
Too little too late... (Score:1)
(http://www.lostpacket.net/)
Re:Cool stuff, but... (Score:2)
(http://zzz.zggg.com/)
Re:Bottleneck. (Score:1)
Today's multiple processor designs are far away from Von Neumann's designs, of course, but just by complex synchronization tricks: cache coherency, multiple syncronized buses, and some other beauty tricks.
Corolarius: we want 64 or more processors on a die, with tons of busses and 0.01 micron 30 layer dies
Re:Cool stuff, but... (Score:2)
(http://www-users.york.ac.uk/~pmj110/)
~phil
Re:Will it help me download porn? (Score:2)
(http://kavlon.org/ | Last Journal: Friday March 21 2003, @02:10PM)
Re:Bottleneck. (Score:2)
Re:Once again, cowboy neal... (Score:2)