Rely on GPU pinning externally #2
Draft
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
…ghost explicitly, so unnecessary. This reverts commit 3bd488c.
Avoids the need to compile with MPI support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Avoids the need to compile with MPI support, which I needed to do when running many independent copies of LAMMPS per node in a workflow.
This change does not preclude running LAMMPS with MPI, but you will have to rely on setting
CUDA_VISIBLE_DEVICESfor each rank when launching LAMMPS (which is recommended mode at ALCF).I've marked this as a Draft for you to consider, noting that another PR to lammps-mace alters the GPU pinning in a different direction.