Skip to content

btl/vader: make the backing file job specific #4767

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, 2018

Conversation

ggouaillardet
Copy link
Contributor

Since 47fd231
the backing file is now in /dev/shm by default. As a consequence,
the backing file name has to include the jobid so more than one job
can run at a time.

Signed-off-by: Gilles Gouaillardet gilles@rist.or.jp

Since open-mpi/ompi@47fd231
the backing file is now in /dev/shm by default. As a consequence,
the backing file name has to include the jobid so more than one job
can run at a time.

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
@ggouaillardet
Copy link
Contributor Author

:bot:mellanox:retest

Copy link
Member

@hjelmn hjelmn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed. I thought I already made this change. Thanks for fixing this.

@hjelmn hjelmn merged commit bb212e0 into open-mpi:master Jan 31, 2018
@ggouaillardet
Copy link
Contributor Author

@jsquyres FYI, that could explain the numerous crashes reported by MTT on the master branch
when btl/vader is used and two jobs (two mpirun or MPI_Comm_spawn()) with two tasks or more each run on the same node at a given time.

@jsquyres
Copy link
Member

@ggouaillardet I was wondering exactly that question. Sweet; thanks for following up.

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