From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Talpey Subject: Re: [PATCH rdma-next 0/3] Support out of order data placement Date: Mon, 12 Jun 2017 18:19:55 -0400 Message-ID: <475e1873-e842-ecb9-d260-34777da57e51@talpey.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=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Parav Pandit , Jason Gunthorpe Cc: 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 6/12/2017 5:32 PM, Parav Pandit wrote: > Hi Tom, ... >> >> I agree with Jason, the bit should be 1 by default, if defined as you propose. >> Out-of-order is the norm, not the exception, for ULPs. >> Honestly, I think you should perhaps consider making it the default on your >> devices, and allowing only MLX-aware ULPs to turn it off. >> > > There can be cases in deployment where responder has support for receiving out-of-order, but requester doesn't. Yuck! So this needs to be negotiated end-to-end, and by the upper layer? Talk about barriers to adoption, and opportunities for disaster. Tom. -- 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