Doug Ledford wrote:
On Thu, 2007-10-11 at 18:51 -0700, Sean Hefty wrote:
I'm more referring to when you call rdma_bind_addr to bind to your
device before you call rdma_connect. In that instance, your address
isn't for the eventual destination, but just to bind you to your local
rdma device. For that, an rdma_bind_dev that took an ibv context and a
port number on that device would avoid having to specify an IP address
that you don't really care about.
Maybe I'm missing something, but you would still use IP addressing to identify
the remote system, which requires IPoIB anyway. My expectation is that the side
that calls rdma_connect() would usually call rdma_resolve_addr(), and not use
rdma_bind_addr(). This way the local device binding occurs based on the routing
tables to the remote address.
Think multiport cards and wanting to use a specific port (for load
balancing or other reasons).
But IP addresses associated with IPoIB and iWARP netdevs _do_ map to a
specific port, yes?
------------------------------------------------------------------------
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
