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 15:41:35 -0600 Message-ID: <20170612214135.GB30578@obsidianresearch.com> References: <20170612064918.12510-1-leon@kernel.org> <1497281280.2770.1.camel@wdc.com> <20170612162917.GA11993@obsidianresearch.com> <20170612164343.GA12435@obsidianresearch.com> <20170612165536.GB12435@obsidianresearch.com> <6747e257-67b0-a364-be21-04f73ef82ffe@talpey.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 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.. Is this actually some kind of selective retransmit scheme? 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