Hi James, Sorry for the late response, my system was down and I just got it fixed.
> Is there a benefit to having rdmav_create_qp() take generic > parameters if the application needs to understand the type of QP (IB, > iWARP, etc.) created and the transport specific communication manager > calls that are needed to manipulate it? > > Would it make more sense if the QP create command was also transport > specific? My opinion is that the create_qp taking generic parameters is correct, only subsequent calls may need to use transport specific calls/arguments. Infact rdma_create_qp uses the ibv_create_qp (now changed to rdmav_create_qp) call internally. PS : What is the opinion on this patchset ? Thanks, - KK _______________________________________________ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
