Hi Dimtris, > > It seems RDMA RC is completely optional, only the default/standardized way of > exchanging parameters and any custom way will do. > > Most helpful, thank you. May I ask the limitation that you are facing with rdmacm due to which (a) you want to avoid it and ready to do extra code for IP to right GID mapping for RoCEv2. (b) implement new connection management With that some how you are also ensuring that both packets (connection management via some socket) and rdma_v2 follow the same path in network? I am curious to know how are you going to ensure this at cluster scale? If you can please share it, it will be useful to me. Parav > > Dimitris > > On Sat, Feb 1, 2020 at 12:39 AM Leon Romanovsky <leon@xxxxxxxxxx> wrote: > > > > On Fri, Jan 31, 2020 at 09:00:24PM -0800, Dimitrios Dimitropoulos wrote: > > > Hi, > > > > > > I'm looking to connect an RDMA hardware accelerator to a Centos 8.0 > > > server with RoCE_V2 capability. > > > > > > Is there a way to implement RDMA RC functionality without invoking > > > the Connection Manager (skipping the rdma_create_event_channel()) ? > > > Perhaps with a simple exchange of the necessary information through > > > an external protocol, say UDP packets ? And then initialize the QPs > > > with the received parameters. > > > > > > You can do it without RDMA-CM, see libibverbs//examples/rc_pingpong.c > > for exactly that. > > > > Thanks
