4 ms·
This is how the ideal machine architecture should look like.. Massive parallelism, as in every cell is a core. Implicit transport- as in every core without ins
by OneTimePetes 5y ago
This is how the ideal machine architecture should look like..
Massive parallelism, as in every cell is a core.
Implicit transport- as in every core without instructions to handle data, forwards it to the next core.
Packages can contain instructions for cores.
A program is nothing but data flowing through the area, marshalled into streams by the embedded instructions within the data.
If a core is not busy, it can switch "location" todo the task of a busy core, thus the computational substrate is as big as the traversing packages need it be. The location is virtual, the core assigned to a package is real.
The output is nothing but little blackholes, swallowing the result from the universe.
This is how our universes simulation architecture looks like.
- holoduke 5y agoA bit how shader units are implemented right
- OneTimePetes 5y agoYes.. and you can see the emergency of what one could call physics as properties of the data flow. You have a light cone, as in data, can not move faster then the processing speed from field to field. You can even remove parts of the universe temporary, as long as its out of reach of the other parts.
- pyinstallwoes 5y agoThat's a bit what Dave is working on with https://movablefeastmachine.org/ https://movablefeastmachine.org/ no? See: https://www.cs.unm.edu/~ackley/#rh-is https://www.cs.unm.edu/~ackley/#rh-is
- pyinstallwoes 5y agoOr also mov based architectures?