Well the idea is that your program the CPU to er.. BE the program, and nothing else. It's sort of like turning a program into a piece of hardware. So you program it for one small task, then all it can do from then on is that one task (Till you reprogram it). So they can't really be used for random general purpose tasks which is what most everything you do is.
Most computer peripherals and electronic devices are full of these processors (generally just a few) already. A video recorder would have one for mpeg compression, one for color conversion, etc... Then a general purpose processor for the UI (Buttons/viewfinder) They work well for commonly used fixed tasks.
Placing a massive general purpose OS on a set of them would be virtually unthinkable. You'd need maybe a million of them. And then you'd still need a general purpose CPU (or a few) to run your programs using them as the building blocks or another several dozen to several thousand per program you were runnning. And in practice, writing code for such architectures even when the outcome is well constrained has turned out to be quite difficult.
It's not that it's like impossible or that in the future with 50 million core ships that such things may not be the way things are done in the future, but it's not going to happen any time soon, but with a 1000 core chip /today/ there are practical uses for it, but not as a replacement for an intel (or amd) general purpose CPU, rather an adjunct for say rendering high res 3d images, cracking ciphers, protein folding etc, pretty much the same thing that GPUs are now already being used for. But having one say off the PCI bus and more local to the main CPU would be nice.
Most computer peripherals and electronic devices are full of these processors (generally just a few) already. A video recorder would have one for mpeg compression, one for color conversion, etc... Then a general purpose processor for the UI (Buttons/viewfinder) They work well for commonly used fixed tasks.
Placing a massive general purpose OS on a set of them would be virtually unthinkable. You'd need maybe a million of them. And then you'd still need a general purpose CPU (or a few) to run your programs using them as the building blocks or another several dozen to several thousand per program you were runnning. And in practice, writing code for such architectures even when the outcome is well constrained has turned out to be quite difficult.
It's not that it's like impossible or that in the future with 50 million core ships that such things may not be the way things are done in the future, but it's not going to happen any time soon, but with a 1000 core chip /today/ there are practical uses for it, but not as a replacement for an intel (or amd) general purpose CPU, rather an adjunct for say rendering high res 3d images, cracking ciphers, protein folding etc, pretty much the same thing that GPUs are now already being used for. But having one say off the PCI bus and more local to the main CPU would be nice.
My Computer
- Computer Manufacturer/Model Number
- Scratch built
- OS
- Windows 7 x64 Ultimate
- CPU
- i7 960
- Motherboard
- Asus P6X58D
- Memory
- 12 Gig Corsair Dominator
- Graphics Card(s)
- Nvidia 480
- Sound Card
- Maudio Delta 44 + breakout box
- Monitor(s) Displays
- Dell UltraSharp U2410 24in and Samsung 21 dual monitors
- Screen Resolution
- 1920x1200 and 1280x1024
- Hard Drives
- Primary: Intel X-25M G2 160G SSD
Secondary: Segate baracuda 1.0 TB
HDs in AHCI mode.
- PSU
- Corasair TX850
- Case
- Cooler Master HAF
- Cooling
- Corsair H50
- Keyboard
- Logitech G15 + N52 game pad
- Mouse
- Logitech MX518
- Internet Speed
- 15kbs down 4.5kbps up
- Other Info
- WEI 7.6
CPU & RAM 7.6
Graphics 7.9
Hard disk 7.7
