Fixed rdma multi device connect failed issue #1402
Closed
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
* The root cause is that if you specified the rdma_device in GFLAGS, the rdma_helper will alloc the pd in the specified device. But when create the cm_id it's bind to the first device. So the pd is not match and create qp will return failed.
Closed
|
Hi, 我们后续计划不再维护单独的RDMA分支，而是将RDMA功能合入master，相关PR：#1836 |
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.
The root cause is that if you specified the rdma_device in GFLAGS, the rdma_helper will alloc the pd in the specified device. But in RdmaCommunicationManager::Create() the cm_id will always bind to the first device. So the pd is not matched and create qp will return failed. #1401