Fix buffer posting and FI_EAGAIN #26617
Merged
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
jhh67
force-pushed
the
T7059
branch
4 times, most recently
from
6fc3bf0 to
4262dd0
Compare
When a receive buffer is flagged as full via FI_MULTI_RECV re-post it immediately while libfabric fills the other buffer. Also, when fi_recvmsg returns FI_EAGAIN try again after calling fi_cq_read to progress the endpoint. Signed-off-by: John H. Hartman <[email protected]>
jabraham17
approved these changes
Feb 11, 2025
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.
When a receive buffer is flagged as full via
FI_MULTI_RECVre-post it immediately whilelibfabricfills the other buffer.Also, when
fi_recvmsgreturnsFI_EAGAINtry again after callingfi_cq_readto progress the endpoint.Resolves https://github.com/Cray/chapel-private/issues/7059.
Resolves https://github.com/Cray/chapel-private/issues/7066.