v5.0: btl/sm: avoid using xpmem for fast boxes #9954
Merged
Conversation
This file contains hidden or 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
jsquyres
changed the title
|
@hppritcha I think this failed because there is no -x in the commit. |
xpmem has different behvior than other shared memory support mechanisms. in particular, any xpmem-attached regions in a process will become invalid once the exporting process exits. Under certain circumstances, this behavior can result in SIGBUS errors during mpi finalize. Related to open-mpi#9868 Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit 8bac539)
hppritcha
force-pushed
the
topic/no_xpmem_for_fboxes_v5.0.x
branch
from
0d5dabc to
7d3f868
Compare
awlauria
approved these changes
Feb 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
xpmem has different behvior than other shared memory support mechanisms.
in particular, any xpmem-attached regions in a process will become invalid
once the exporting process exits.
Under certain circumstances, this behavior can result in SIGBUS errors
during mpi finalize.
Related to #9868
Signed-off-by: Howard Pritchard [email protected]