On Tue, Mar 4, 2014 at 11:31 PM, Hefty, Sean <[email protected]> wrote: > Clients should not be made aware of how the resolution was done. The RDMA CM > needs to abstract that problem. Alternate mechanisms may be usable, but > there aren't exactly a whole lot of options available. The client could use > native IB addressing at this point if it does not want to rely on address > translation.
No, native IB addressing isn't an option for this and many other applications. they want to use IP addressing. We have to make sure that our IP --> RDMA address resolving which uses neighbour lookup is robust under the real life schemes I brought which makes the RC connection / UD session established based on this resolution to be totally broken. So given the fact that we have a solution for large scale through native IB addressing that offloads the address and route resolution -- what's your thinking on my suggestion to make address resolution for rdma-cm endpoints creates with the non native IB port space to use solicit neighbour lookup (e.g avoid arp cache usage?) Or. -- 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
