v4.1.x: Fix wrong affinity under LSF with membind option. #9232
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.
When submitting an mpi job with LSF option:
-R "affinity[core:membind=localprefer:distribute=balance]",
the affinity produced by ompi is incorrect.
This solution is to to drop memory binding options in
LSB_AFFINITY_HOSTFILE and keep them for future use.
Longer term there is an "RM_CPUTASK" env variable
that could be leveraged - but this would need additional
work.
Signed-off-by: Austen Lauria [email protected]
(cherry picked from commit b4b9b87)