On Mon, Mar 3, 2014 at 7:15 PM, Hefty, Sean <[email protected]> wrote: [...] > If a CM REQ actually gets to the remote side, it could be rejected as an > invalid GID, and the client could retry the request.
Retrying the request is practically calling 1. rdma_resolve_addr 2. rdma_resolve_route 3. rdma_connect where step #1 would get wrong GID from the client arp cache and hence step #3 would result in a reject and so on... I am starting to think that the rdma address resolution must not make use of the arp cache, or at least provide applications the API to dictate that ARP request must be sent, how this sounds? -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
