[ewg] rdma/cm: disallow loopback address for iwarp devices
Jason Gunthorpe
jgunthorpe at obsidianresearch.com
Mon Feb 8 14:09:03 PST 2010
On Mon, Feb 08, 2010 at 04:56:23PM -0500, Jeff Squyres wrote:
> DESCRIPTION
> Associates a source address with an rdma_cm_id. The address may be
> wildcarded. If binding to a specific local address, the rdma_cm_id
> will also be bound to a local RDMA device.
> What RDMA device is bound to when you use 127.0.0.1? I'm not 100%
> sure, but I think that this might be where we got the rationale that
> we didn't need additional LOOPBACK tests in OMPI... (if anyone else
> agrees with this interpretation, then it's at least one argument
> that allowing binding to LOOPBACK devices *is* a change in
> semantics, and therefore should be treated extremely carefully)
This statement is trying to say that if a source address is given then
the rdma_cm_id will be bound to a device. Designating which APIs bind
the device is important for the API user, once the device is bound you
can allocate resource against it.
It doesn't matter which device is picked, that is up to the kernel.
For instance if the the same IP is assigned to multiple RDMA devices
then the kernel will pick one.
Jason
More information about the ewg
mailing list