>I'm using the new rdma cma interface and i've perhaps stumbled onto a bug. I'm >trying to bind to port 9999 on both IB ports of a >mthca device. The IPoIB interfaces for the HCA are configured as two seperate >subnets. The second rdma_listen() always fails with
How are you binding the address to the rdma_cm_id? Are you binding based on the port number only, or binding to a port and IP address. >EBUSY. Maybe this is a limitation in the CMA design, but TCP stacks allow >binding to the same port on different ip addresses. And What's happening is that the both listen requests are being mapped to the same service ID. The request listen is then failing. The IB CM maps listens to a device, and not a port on that device. Fixing this will require adding some additional demultiplexing code to the CMA >the CMA interface allows it too as long as the two ip addresses map to >different IB devices. Whether this should work or not, I am >seeing a crash when I try to destroy the cm_id after the rdma_listen() failure. The crash shouldn't be happening. The cma_ib_listen() should clear the cm_id pointer after destroying it to prevent it from being destroyed a second time. I'll get a patch for this shortly. - 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
