> > > > - this doesn't change anything. Also, AHs are already > > > port-specific. So, I don't see any issue in this regard. > > > > The current scheme infers the protocol of the AH from the current > > configuration of the port, which is a crazy API when the port's > > protocol can change on the fly. > > Maybe the solution is to make the protocol selection explicit throughout the APIs > and associate it with a QP, rather than attempting to list all transport protocols that > a port can support. Do you mean requiring the application to pick the protocol? -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
