Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:46218 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752927AbaCAQAd (ORCPT ); Sat, 1 Mar 2014 11:00:33 -0500 Date: Sat, 1 Mar 2014 11:00:22 -0500 From: Jeff Layton To: Chuck Lever Cc: Wendy Cheng , Tom Talpey , "linux-rdma@vger.kernel.org" , Linux NFS Mailing List , Shirley Ma Subject: Re: Proposal for simplifying NFS/RDMA client memory registration Message-ID: <20140301110022.417eb088@tlielax.poochiereds.net> In-Reply-To: References: <01C4496A-F074-4F72-9DF0-6076C05E8A1F@oracle.com> <53110287.9000400@talpey.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Fri, 28 Feb 2014 21:59:00 -0500 Chuck Lever wrote: > Hi Wendy- > > On Feb 28, 2014, at 5:26 PM, Wendy Cheng wrote: > > > On Fri, Feb 28, 2014 at 2:20 PM, Wendy Cheng wrote: > >> ni i...On Fri, Feb 28, 2014 at 1:41 PM, Tom Talpey wrote: > >>> > >>> On 2/26/2014 8:44 AM, Chuck Lever wrote: > >>>> > >>>> Hi- > >>>> > >>>> Shirley Ma and I are reviving work on the NFS/RDMA client code base in > >>>> the Linux kernel. So far we've built and run functional tests to determine > >>>> what is working and what is broken. > >>>> > >>>> [snip] > >> > >> > >>>> > >>>> ALLPHYSICAL - Usually fast, but not safe as it exposes client memory. > >>>> All HCAs support this mode. > >>> > >>> > >>> Not safe is an understatement. It exposes all of client physical > >>> memory to the peer, for both read and write. A simple pointer error > >>> on the server will silently corrupt the client. This mode was > >>> intended only for testing, and in experimental deployments. > > > > (sorry, resend .. previous reply bounced back due to gmail html format) > > > > Please keep "ALLPHYSICAL" for now - as our embedded system needs it. > > This is just the client side. Confirming that you still need support for the ALLPHYSICAL memory registration mode in the NFS/RDMA client. > > Do you have plans to move to a mode that is less risky? If not, can we depend on you to perform regular testing with ALLPHYSICAL as we update the client code? Do you have any bug fixes you?d like to merge upstream? > Also, given that ALLPHYSICAL isn't considered safe, we should at the very least require some sort of explicit opt-in before allowing it to be used. Perhaps either a Kconfig option, or maybe a runtime switch like a module parm? Wendy, would that be acceptable? -- Jeff Layton