The app _usually_ doesn't care. See NFS discussion for a client app that does care. Also, providers DO care. Because of this issue, the chelsio iwarp provider right now has to allocate its own ephemeral ports at connect time. This logic should be moved into the IWCM or maybe the CMA and an explicit bind() operation be exported by the iwarp providers to allow the IWCM or CMA to track all port allocations.
Somehow I didn't receive Steve's response. Anyway, I'm referring to apps that don't specify which port to use as the one's that don't care, versus those that do want to know their port.
In reality, the port space for RDMA connections over IB is distinct from the TCP port space. No attempt is made to coordinate between the two, and I am not convinced that those two port spaces should be one and the same. This is where I believe there's disconnect.
- Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
