Hi Jason, > -----Original Message----- > From: Jason Gunthorpe [mailto:jgunthorpe@xxxxxxxxxxxxxxxxxxxx] > Sent: Monday, June 12, 2017 12:32 PM > To: Parav Pandit <parav@xxxxxxxxxxxx> > Cc: Bart Van Assche <Bart.VanAssche@xxxxxxxxxxx>; leon@xxxxxxxxxx; > dledford@xxxxxxxxxx; linux-rdma@xxxxxxxxxxxxxxx; Idan Burstein > <idanb@xxxxxxxxxxxx> > Subject: Re: [PATCH rdma-next 0/3] Support out of order data placement > > On Mon, Jun 12, 2017 at 05:28:00PM +0000, Parav Pandit wrote: > > > > Exactly - all spec conformant ULPs are compatible with enabling this > > > new function of mlx5. > > > This per QP attribute is for read and write both. So responder can receive > out-of-order read responses. > > And HCA's QP need to be told to accept it that way, which by default > doesn't. > > I think this one flag is conflating too many things then. > 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. > Obviously sending out of order packets is not spec conformant, and I don't > think your discussion is clear enough, as this change to send side certainly > was not clear to me. > Ok. I can make Documentation more elaborate that describe summary of this discussion + Bart's point. > I'm not excited about a new end-to-end flag without some kind of > negotiation scheme, and I'm not excited about this being in any of the > common APIs. Many applications do out-of-band negotiation or static configuration and its unrelated to the patchset. So lack of negotiation shouldn't be issue. Its outside the scope of this verb extension anyway. > > 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. > > 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
