Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed two issues with RDMA connection establishment. #188

Merged
merged 1 commit into from
Jun 30, 2016

Conversation

hernando
Copy link

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.

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.
@hernando
Copy link
Author

FYI @dardok

@hernando
Copy link
Author

Retest this please.

@hernando
Copy link
Author

@eile, @tribal-tec could you review?

@tribal-tec
Copy link
Member

Good to me, although I'm not an expert here.

@eile eile merged commit 7ffbfab into Eyescale:master Jun 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants