Sean Hefty wrote:
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?
This is what I ended up needing to do for Windows (but for other reasons), so
I'm not against adding this to the library.
I did this too for Chelsio's NetDirect provider...
I'm undecided on the best way to expose this. Always enabled? Enabled during
the build? Enabled through a new API? Other?
I think it should be enabled by default to resolve the issue once and
for all.
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
