Re: [PATCH rdma-next 0/3] Support out of order data placement

Jason Gunthorpe
2017-06-12T17:32:21Z

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.

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.

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.

Perhaps it should be in libmlx5 instead.

Jason