Direct Core access memory type provided, for speedup singe mote execution #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There provided mote execution speedup via using direct mote's corelib-memory access.
For ordinary corelib memory access done via clone-per-mote instances of original coer-lib. Before tick mote, whole memory of clone copyes into corelib-memory, and after tick it copies back. All operations with memory contents goes with that cloned memory per each mote.
If simulation have only single mote instance for moteType, no need save contents of corelib memory, we can use it directly.
Here provided DirecCoreMemory interface that pass this direc-access. This interface used by mote, when it is single in simulation.
Results of profling in simulation of 2 different motes:
TODO: now need to look for ways to scale this techniks on multiple mote instances. Simplest aproach i see - just make individual corelib for each mote.
there no need further DirectAccess optimisations, until 4log cpu wastes are solved.