Skip to content

btl/sm: avoid using xpmem for fast boxes #9880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 31, 2022

Conversation

hppritcha
Copy link
Member

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]

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]>
@jsquyres
Copy link
Member

@hppritcha Will this be applicable to older release branches (v4.1.x)?

@hppritcha
Copy link
Member Author

Yes it would.

@gpaulsen
Copy link
Member

looks good to me.

@hppritcha hppritcha merged commit de4fe77 into open-mpi:master Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants