Add CNMeM support using global MemoryHandler #12
Merged
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.
This is a different approach to adding a memory pool than my last PR -- this moves the pool management to a global singleton, independent of Caffe's singleton, to avoid any unintended side-effects of the thread-local storage used in the multi-gpu code.
Destruction of the memory pool's resources is now handled safely using an activator object (MemoryHandlerActivator) that initializes the pool on construction and finalizes it safely on destruction.