Hey Sean,
It seems like kernel RDMA protocols are all getting IANA-assigned port
numbers that alleviates the need for TCP/RDMA port unification. NFSRDMA
and RDS are two. But user applications like mvapich2 and other mpis
often let the stack choose a local port number on-which to bind/listen.
Would you reconsider moving the tcp/rdma port unification changes up
into librdmacm? The benefit is that this will resolve the issue in a
manner that can flow into the distros and not affect the linux kernel.
So librdmacm could, if configured to support this, just allocate and
bind a user socket to reserve the TCP port on behalf of the rdma
application. The code would be similar to the kernel patch...
Thoughts?
Thanks,
Steve.
_______________________________________________
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
