2 ms·
I kinda like the idea of this, and that's also one of the reasons I find architectures like the Adapteva Epiphany (the chip that makes the Parallella [1] intere
by vidarh 10y ago
I kinda like the idea of this, and that's also one of the reasons I find architectures like the Adapteva Epiphany (the chip that makes the Parallella [1] interesting) interesting. At the moment they're more curiosities because each core is so weak, but they're at least exploring the space of architectures designed for ultra-high core counts (their latest chip is 1024 cores [2], and what makes them different from GPUs is that these are 1024 fully independent cores, running different instruction streams).
The problem, though, remains, that for most systems, unless each core is tremendously weak, you can run most of the ongoing tasks on a typical current desktop system on a tiny timeslice of a single core.
OSs certainly can paralleise more. E.g. AmigaOS relied far more on using multitasking as a basic OS primitive 30 years ago than most modern OSs, because message passing was exceedingly cheap (no memory protection, context switched involved moving a few registers). Something as simple as cut and paste could involve nearly a dozen processes (device drivers for mouse and keyboard, input handler, console device and higher level console handler, a process specifically managing the console clipboard (other apps might handle it themselves), the clipboard handler, the clipboard device, a filesystem handler for wherever the clipboard was mapped, the underlying disk device - usually ramdisk but could be anything, and more depending on setup). That was to make latency predictable first and foremost, at the cost of throughput, but the overall model could be adapted.
But part of the challenge is to write applications this way without just ending up being bottlenecked on the message exchanges.
Even if you can make that cheap enough, we still have the problem of the vast number of tasks that are simply very hard to parallelise. For some of them splitting them up and spreading them out certainly could make things like pipelining processing help us cut latency when something is done repeatedly, but whatever we do, we will have big challenges ahead.
[1] https://www.parallella.org https://www.parallella.org
[2] http://www.adapteva.com/announcements/epiphany-v-a-1024-core-64-bit-risc-processor/ http://www.adapteva.com/announcements/epiphany-v-a-1024-core...