On Mon, Jun 12, 2017 at 05:46:34PM +0000, Parav Pandit wrote: > Too many flags just confuses end-user for > read/write/requester/responder etc. Also there isn't well > established use case either where user wants to do only certain > things. Your original discussion said this optimized cases on Rx when the fabric went out of order, eg repath, etc. That seems well defined enough to be a dedicated flag, default to on, etc. Sending packets out of order is an entirely different beast, and sounds like it would also require additional configuration, as IBA doesn't even have an existing way to describe a set of paths to choose between. How are the TX paths choosen? That need to be documented before this could even be considered for the common API. This is why I think one flag is a bad idea. > > Perhaps it should be in libmlx5 instead. > > We think that its best usable through ibv_modify_qp because it's > really simple enough and well documented which will address inputs > given in this discussion. That isn't really the criteria to be in the common API now that we have the libmlx5 approach. Jason -- 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
