Pavel Shamis (Pasha) wrote: > The only reason for this changes is the fact that for IB devices we > prefer to use our own open mpi connection managers. In case if we will > decide to use RDMA-CM for all devices the number of changes will be zero...
whatever, currently, this change is still there, and best if you remove it and find another way to set this predicate. > So we decided to use the current ompi code as is, in future maybe we will > implement own ompi rdmacm code that will not have all this work around flows. just to make sure I am with you, all in all, only one patch is proposed to ompi for rdmaoe support and is the patch which we discuss above, this patch does three things: 1. changes BTL_OPENIB_CONNECT_BASE_CHECK_IF_NOT_IB to look on the port transport type 2. if the port transport is rdmaoe don't run loopback connections on IB 3. some change in the qp destroy logic 4. that's it... correct? can you comment on #2? why loopback connections aren't supported? Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
