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

Jason Gunthorpe
2017-07-19T17:12:11Z

On Wed, Jul 19, 2017 at 05:33:52AM +0000, Parav Pandit wrote:

> It does guarantee that writes don't bypass writes and reads don't bypass reads (Table 79), and transport operations are executed in their *message* order (C9-28):
> "A responder shall execute SEND requests, RDMA WRITE requests
> and ATOMIC Operation requests in the message order in which
> they are received."

At a minimum, you need to include a version of table 79 in your
documentation that reflects the modified WR ordering rules for this
mode, and I'm not sure we should continue to call this thing a 'RC QP'
at all to avoid so much confusion.

Particularly since this new thing is not really wire interoperable
with the existing RC QP I don't think it should be the same thing in
the API.

I recommend you rework this patch series to introduce a relaxed RC QP
type instead of using a flag..

Jason