Skip to content

Conversation

lcy0816
Copy link

@lcy0816 lcy0816 commented Sep 1, 2016

The current implementation of class VolatileMemAllocator does not support retrieval operations so it is not possible to temporarily forget cached durable objects efficiently like class NonVolatileMemAllocator does, logically, volatile memory should be retrievable for durable object graphs in a applications/frameworks run-time session.
In addition, durable native computing must based on retrievable interface, therefore the VolatileMemAllocator should implement retrievable interface to support forgettable object graphs and durable native computing.

@AI-Memory AI-Memory merged commit dcfee31 into NonVolatileComputing:master Sep 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants