From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH rdma-next 0/3] Support out of order data placement Date: Mon, 12 Jun 2017 16:21:38 -0600 Message-ID: <20170612222138.GA552@obsidianresearch.com> References: <20170612164343.GA12435@obsidianresearch.com> <20170612165536.GB12435@obsidianresearch.com> <6747e257-67b0-a364-be21-04f73ef82ffe@talpey.com> <20170612214135.GB30578@obsidianresearch.com> <20170612220730.GA32510@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Parav Pandit Cc: Tom Talpey , Bart Van Assche , "leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , "dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Idan Burstein List-Id: linux-rdma@vger.kernel.org On Mon, Jun 12, 2017 at 10:16:26PM +0000, Parav Pandit wrote: > > And I keep asking you to explain what is different about the transmitter > > side. > Above sequence explains read_response_transmitter behavior. but that has no impact on the other side of the QP - it does not care if they were processed successefully or a NACK is sent and retransmit is needed. Still not seeing any explanation for why negotiation is required, and I'm getting sick of asking, please craft a response with your internal team. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html