Allow Chapel programs with COMM=ofi to use explicit transparent huge pages #24971
Conversation
This file contains 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
Signed-off-by: Jade Abraham <jade.abraham@hpe.com>
Signed-off-by: Jade Abraham <jade.abraham@hpe.com>
jhh67
requested changes
May 2, 2024
Signed-off-by: Jade Abraham <jade.abraham@hpe.com>
This was referenced May 2, 2024
jhh67
approved these changes
May 3, 2024
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.
This PR adds a new runtime variable,
CHPL_RT_COMM_OFI_THP_HINT, which controls if the OFI comm layer will use transparent huge pages to allocate memory. The default value is false, except when the provider being used is EFA. The default is true for EFA, since EFA is severely limited in the number of pages it can register.This PR also updates the docs for using Chapel on AWS to explain how to enable and use transparent huge pages.
This PR requires #24969 to be merged first
Tested on AWS
[Reviewed by @jhh67]