Decide on a memory object model - Githubissues

HadrienG2 / phalanstery

Experiments with user-mode tasking in Ada

GNU General Public License v3.0

4 stars 0 forks source link

Decide on a memory object model #3

Open HadrienG2 opened 8 years ago

HadrienG2 commented 8 years ago

The chosen memory object model should, to the best possible extent, deal with the following concerns:

Implicit synchronization (no need for explicit event), see e.g. futures
Non-uniform memory access within a shared memory system
Non-shared memory (e.g. distributed and heterogeneous systems, scratchpads...)
Data transfer and serialization issues

For futurization, there seems to be a lot of interesting ongoing Ada projects, that should be studied. See, for example, https://groups.google.com/forum/#!topic/comp.lang.ada/v0ZXkaG8rek

HadrienG2 commented 8 years ago

A possibly interesting model would be to make accesses to a memory region mutually exclusive, but allow "breaking up" the associated memory object across threads.