On Mon, Jun 12, 2017 at 09:59:22PM +0000, Parav Pandit wrote: > Hi Jason, > > > From: Jason Gunthorpe [mailto:jgunthorpe@xxxxxxxxxxxxxxxxxxxx] > > Sent: Monday, June 12, 2017 4:42 PM > > To: Parav Pandit <parav@xxxxxxxxxxxx> > > Cc: Tom Talpey <tom@xxxxxxxxxx>; 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 09:32:30PM +0000, Parav Pandit wrote: > > > > > There can be cases in deployment where responder has support for > > > receiving out-of-order, but requester doesn't. Read responses > > > > You still haven't explained at all what the transmitter side does differently.. > > Let's say > Read-1 > Read-2 are issued by requester. > > For some reason read response for each read arrived via different > path to requester, If ooo is enabled on a QP they will be processed > correctly. Else read responses for 2nd read could be dropped. This is still only discussing the reciever side of a QP. > transmitter of read responder is different when ooo is enabled. And I keep asking you to explain what is different about the transmitter side. 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
