Fixed two issues with RDMA connection establishment. #188
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.
In some systems rdma_getaddrinfo returns a list of addresses where
the first is from the AF_IB familiy. Apparently this only happens
in the client and the server, which binds using AF_INET[6] rejects
the connection.
In route resolution it is necessary to wait for the event
RDMA_CM_EVENT_ROUTE_RESOLVED fter using rdma_set_option when the
rdma_addrinfo struct contains routing information.