The CPU Redefined: AMD Torrenze and Intel CSI

janp writes "In the near future the Central Processing Unit (CPU) will not be as central anymore. AMD has announced the Torrenza platform that revives the concept of co-processors. Intel is also taking steps in this direction with the announcement of the CSI. With these technologies in the future we can put special chips (GPU's, APU's, etc. etc.) directly on the motherboard in a special socket. Hardware.Info has published a clear introduction to AMD Torrenza and Intel CSI and sneak peaks into the future of processors."

Comments

huh?

[mastershake_phd]

Werent the first co-processors FPUs. Arent they now integrated into the CPU? By having all these thing sin one chip they will have much lower latency with communicating between themselves. I think all in one multi-core chips is the future if you ask me.

Re:huh?

[Chrisq]

I think it has to do with the number of configuration options. Even if technology was able to fabricate one super chip with the best possible GPU and sound processor might be great for some people, but others would be better off with extra general purpose cores, cache, etc. The flexibility of "mix and match" probably outweigh the advantages of having the separate components on a single chip

Re:huh?

[MrFlibbs]

The CPUs will still be multi-core. They will also integrate as many features as makes sense. However, there are limits on how big the die can be and remain feasible for high volume manufacturing. Using an external co-processor is both more flexible and more powerful.

The interesting thing about this whole co-processor approach is that the same interface used to connect multiple CPUs to each other is being opened up for other processing devices. This makes it possible to mix and match cores as desired. For example, you could build a mesh of multi-core CPUs in a more "normal" configuration, or you could mate each CPU with a DSP-like number cruncher and make a special purpose "supercomputer". It will interesting to see what types of compute beasts will emerge from this.

Re:huh?

[Mr2cents]

Adapting another quote: "If you want to create a better computer, you'll you'll end up with an Amiga". It's more or less what they're describing here. Amiga made heavy use of coprocessors back in the days. It could do some quite heavy stuff (well, at the time), while the CPU usage stayed below 10%.

One cool thing I discovered while I was learning to program was that you could make one of the coprocessors interrupt when the electon beam of the monitor was at a certain position. Pretty nifty.

BTW, for those who are too young/old to remember, those were the days of dos, and friends of mine were bragging with their 16 color EGA cards. Amiga had 4096 colors at the time.

Re:huh?

[TheThiefMaster]

It's a cost and feasibility thing. The original FPUs were separate because they were expensive, not everyone needed them, and it was impractical to integrate them into the cpu because it would make the die too large and result in large numbers of failed chips. They became part of the chip later once the design was refined and scaled down.

The same applies to trying to integrate GPUs into the CPU, at the moment a top-end GPU is too large and expensive to integrate, and not everyone needs one. The move to having a GPU in a CPU socket should cut a lot of cost because the GPU manufacturers won't have to create an add-in-card to go with the GPU, they can just design the chip to plug straight into a standardised socket.

At the same time low-end GPUs are small and cheap enough that they are being integrated into motherboards, integrating a basic GPU into the CPU seems like a good next move, and the major cpu manufacturers seem to agree. IIRC Via's smallest boards integrate a basic cpu, northbridge and gpu into one chip? AMD are definitely planning it with their aptly named "Fusion". *Checks wikipedia* Yeah, Via's is called "CoreFusion".

Still, you are right, all-in-one cpus are the future, we're just not quite there yet.

Re:huh?

[walt-sjc]

Ahh - the Amiga. My favorite machine during that era. I got my A1000 the first day it was available. Modern OS's could still learn a lot from that 20 year old OS. Why oh why are we still using "DOS Compatible" hardware????

Amiga had 4096 colors at the time.

Better put "4096" with a "*" qualifier. You couldn't assign each pixel an exact color - the scheme got you more colors by being able to set a bit that said that the next pixel modifies the previous pixel by "x". In this way, they could get more colors using less memory than traditional X bits per color per pixel schemes (Amiga was a bitplane architecture.)

Anyway, back on topic, I wish that the CPU manufacturers could finally come up with a "generational" standard socket. A well-designed module socket should last as long as an expansion slot standard (ISA,PCI,PCIe) and not change for damn near every model of chip. I should be able to go out and get a one, 2, 4, 8 socket motherboard, and stick any CPU / GPU / DSP module into it I want. Can we please finally shitcan the 1980's motherboard designs?

Re:huh?

[*weasel]

However, there are limits on how big the die can be and remain feasible for high volume manufacturing.

The limits aren't such a big deal.
Quad-core processors are already rolling off the lines and user demand for them doesn't really exist.
They could easily throw together a 2xCPU/1xGPU/1xDSP configuration at similar complexity.
And the market would actually care about that chip.

Re:huh?

[thygrrr]

Nope, the A500 also had 4096 colours in HAM mode. They were basically the same hardware, except the A2000 had different - and more - expansion slots and was a desktop machine while the A500 was a typical home computer/console kind of thingy.

Re:huh?

[Fordiman]

But think. There is definitely money in non-upgradable computers - especially in the office desktop market. The cheaper the all-in-one solution, the more often the customer will upgrade the whole shebang.

Example: in my workplace, we have nice-ass Dells which do almost nothing and store all their data on a massive SAN. They're 2.6GHz beasts with a gig of ram, a 160G HD, and a SWEET ATI vid card each. Now, while I personally make use of it all proper-like, most people here could get along with a 1GHZ/512MRAM/16GHD/Onboard video system.

I think Intel/AMD stands to make a lot of money if they were to build an all-in-one-chip computer, ie: CPU, RAM, Video, Sound, Network, and a generous flash drive on a single chip.

Re: huh?

[Dolda2000]

Still, you are right, all-in-one cpus are the future, we're just not quite there yet.

Actually, no thank you. I've had enough problems ever since they started to integrate more and more peripherals on the motherboard. I'd be troubled if I'd have to choose between either a VMX-less, DDR3-capable chip with the GPU I wanted, a VMX- and DDR3-capable chip with a bad GPU, a VMX-capable but DDR2 chip with a good GPU, or a chip that has all three but an IO-APIC that isn't supported by Linux, or a chip that I could actually use but costs $500.

Instead of gaining those last 10% of performance, I'd prefer a modular architecture, thank you. Whatever is so terribly wrong with PCI-Express anyway?

Re:huh?

[evilviper]

"If you want to create a better computer, you'll you'll end up with an Amiga". It's more or less what they're describing here.

That's what he's describing, but I don't believe for a second that's what it's going to be...

I don't believe for a second practically ANYONE is going to buy an expensive, multi-socket motherboard, just so they can have higher-speed access to their soundcard... Ditto for a "physics" unit.

This exists solely because CPUs are terrible at the same kinds of calculations ASICs/FPGAs are incredible at. That will be the only killer app here.

Video cards are a good example on their own. CPUs are so bad, and GPUs are so good, that transferring huge amounts of raw data over a slow bus (AGP/PCIe) still puts you far ahead of trying to get the CPU to process it directly. And it works so well, the video card companies are making it easier to write programs to run on the GPU.

And GPUs aren't remotely the only case of this. MPEG capture/compression cards, Crypto cards, etc. have been popular for a very long time, because ASICs are extremely fast with those operations, which are extremely slow on CPUs.

The situation is much more like x87 math co-processors of years past, than it is like the Amiga, with independent processors for everything.

It is likely that, in time, integrating a popular subset of ASIC functions into the CPU will become practical, and then our high-end video cards will be simple $10 boards, just grabbing the already-processed data sent by the chip, and outputting it to whatever display.

Then maybe AMD and Intel will finally focus on the problem of interrupts...

Re:huh?

[Archangel Michael]

"most people here could get along with a 1GHZ/512MRAM/16GHD/Onboard video system."

Haven't tried to run Vista yet ... have you.

Re:huh?

[default luser]

Isn't this called "passive backplane" or something? If it already exists for some systems, why not desktop computers?

Early high-end computer systems started out like this, utilizing backplanes like VME. They've been phased-out, because ultimately that modularity was too expensive, and because the shared-bus architecture hurt performance. Hardware devices that used to require multiple cards can now fit on a single chip, and have their own PCIe drop to increase performance. Memory upgrades that used to require multiple cards just to reach 1MB are now eclipsed by 8 and 16-chip configurations on a single DIMM (a specialized expansion slot), and have their own bus to improve performance.

Let's say they went with the Single-board computer design (CPU+memory+bus controller) - now your costs go up, because you have to build multiple "processor cards" for all the different backplanes you want to plug into. ISA backplane - 1 model. PCI backplane - 1 model. PCI + ISA backplane - 1 more model, and it also requires a new specification: the new bus designs have to play nice with the limited I/O space at the back of the card, so you end up either making the bus connector larger, or you end up making certain bus combinations impossible.

With the motherboard and atached bus design, your costs go down because you can provide a mixture of the busses that are the most popular. Thus, you only have one product to design and electrically verify, and only one manufacturing line to test.

Also, when you move to point-to-point architectures like PCI-Express, with a separate backplane you really limit yourself to the slot configurations you can offer. Unlike with a shared bus, with P2P interconnects you have to make sure the backplane layout matches the connector layout exactly. This means you either standardize on ONE configuration (boring), or you put the ports on the processor card (what we are doing).

The only places that still use modular bus designs today are embedded developers, and that's because they still need the expandability and modularity that end-users do not. They also need the backward-compatibility affored by these old bus specifications (VME especially). They pay for it, in terms of performance - most of them bypass the slow backplane of VME or CompactPCI with faster interconnects like Gig/10GigE, Fibre Channel, RapidIO or Infiniband.

CSI?

[BigBadBus]

CSI? De-centralized CPU? Where will they be located; Miami, New York or Las Vegas?

Re:CSI?

[91degrees]

CSI? De-centralized CPU? Where will they be located; Miami, New York or Las Vegas?

Well, clearly, they won't. They're decentralised.

New on NBC, "CSI: Wherever". We even have a song by The Who for the opening credits - "Anyway, Anyhow, Anywhere".

Previous announcements

[G3ckoG33k]

The first details emerged half a year ago:


IBM and Intel Corporation, with support from dozens of other companies, have developed a proposal to enhance PCI Express* technology to address the performance requirements of new usage models, such as visualization and extensible markup language (XML).

The proposal, codenamed "Geneseo," outlines enhancements that will enable faster connectivity between the processor -- the computer's brain -- and application accelerators, and improve the range of design options for hardware developers.


http://www.intel.com/pressroom/archive/releases/20 060927comp_a.htm

Re:Previous announcements

[badfish99]

Since when is XML a new usage model requiring advances in processor design?

Since it became bloatware that is capable of wasting 90% of the processing power of a modern computer.
</sarcasm>

Retro-innovation

[Don_dumb]

Here spins the Wheel Of Reincarnation http://www.catb.org/~esr/jargon/html/W/wheel-of-re incarnation.html watch how everything comes back and then goes away again and then comes back . . .

Slashdot could benefit from a co-processor...

[Mad_Rain]

that revives the concept op co-processors.

Slashdot's computers might benefit from a co-processor, the function of which is to monitor and correct spelling and grammar errors. It would serve like an editor's job, only better, because, you know, it might actually work.

(Bye-bye karma!)

Re:Interesting

[Overzeetop]

You are correct - sockets are just a reincarnation of slots, but less flexible because you're limited to what you can put on a single chip instead of an entire card.

Perhaps the better thing to do would be better slot designs (not that we need more with all the PCI flavors floating around right now) with integrated, defined cooling channels. If you were to make the card spec with a box design rather than a flat card, you could have a non-connector end mate with a cooling trunk and use a squirrel cage (higher volume, quieter, more efficient)fan to ventilate the cards.

Cell Clusters

[Doc Ruby]

How about the Cell uP (first appearing in Playstation3), which embeds a Power core on silicon with a 1.6Tbps token ring connecting up to 8 (more later) "FPUs", extremely fast DSPs. IBM's got 4 of them on a single chip, connected by their "transparent, coherent" bus, a ring of token rings. One Cell can master a slave Cell, and IBM is already debugging 1024 DSP versions, transparently scalable by the compiler or the Power "ringmaster" at runtime.

These little bastards are inherently distributed computing: a microLAN of parallel processors, linkable in a microInternet.

Imagine a Beowulf cluster of those! No, really: a Beowulf cluster of Cells.

AMD competes with...

[Comboman]

AMD will compete by releasing "Law & Order: Central Processing Unit".

Really just two types of processors

[J.R. Random]

There are basically two models of parallelism that are used in practice. One is the Multiple Instruction Multiple Data model, in which you write threaded code with mutexes and and the like for synchronization. The other is Single Instruction Multiple Data, in which you write code that operates on vectors of data in parallel, doing pretty much the same thing on each piece of data. (There are other models of parallelism, like dataflow machines, but they don't have much traction in real life.) Multicore CPUs are MIMD machines, GPUs are SIMD machines. All those other processors -- physics processors, video processors, etc. are just SIMD machines too, which is why Nvidia and ATI could announce that their processors will do physics too, and why folding@home works so well on the new ATI cards. So I suspect that in real life there will be just two types of processors. At least I hope that is the case, because it will be a real mess if application A requires processors X, Y, and Z while application B requires processors X, Q, and T.

Re:As rumored, first addopted by the porn industry

[demonbug]

Prepare to see the pornprocessor soon. I'm not going to give a lot of details here, but it's optimized for specific physics, AI and Graphics

AI? For porn? You have seen porn before, right?