This repository has been archived by the owner on Sep 30, 2022. It is now read-only.
v1.10: Move Memory Allocation Hooks usage from openib #1002
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These changes fix issue open-mpi/ompi#1336 - improve abstractions: opal/memory/linux component should be single place that opeartes with Memory Allocation Hooks. - avoid collisions in case dynamic component open/close: it is safe because it is linked statically. - does not change original behaivour.
Thanks Igor Ivanov for the review.
igor-ivanov
changed the title
igor-ivanov
changed the title
|
Test PASSed. |
|
👍 |
rhc54
pushed a commit
that referenced
this pull request
Mar 22, 2016
v1.10: Move Memory Allocation Hooks usage from openib
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes open-mpi/ompi#1336
See related PR in ompi/trunk open-mpi/ompi#1351
:bot:assign: @jsquyres
:bot🏷️bug
:bot:milestone:v1.10.3
ompi-trunk:
open-mpi/ompi@d9eefef
open-mpi/ompi@477991b
open-mpi/ompi@5c685e2
@ggouaillardet please look at to double check