Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp6671334ybn; Mon, 30 Sep 2019 01:43:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqxinPBoyV50evA5N8SbEgScoQFkCynQSGTtfS3Xyzz8kBu7Dk5h2SL9MSspqqKHJSNU8PhT X-Received: by 2002:a17:906:c822:: with SMTP id dd2mr15918519ejb.165.1569832998058; Mon, 30 Sep 2019 01:43:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569832998; cv=none; d=google.com; s=arc-20160816; b=XQ5R/3IHq/SJUugasJ1xsIel3ZyhyYBQTfnq/7VtKFfEeMShBMrWJAUCSg+wdRiXVy 7P4u1f9YEW4uHt6bVu308ObTZq//StyYzRMYVIhia0u566G26+pI5DfBN9tOrtxQb7ez yJ3fG2OLw/t2SOiFEEvFJnmydhXNIeZDX8jM/02UZvb1HSB9m1HWxWoTE1gVcNDPaxwr H7Duo+U5shxGeUO7PnySTyWKq5MW9OQC90VrJIsqRmntv9KGEq3B1lDINpuftsSx55wR cX/bNuC8e/xThB1+DnEENK+MCo7F45Q9C3Q2rwuJv8YFGdKpc5Pk4shBELnDHMQi95sH EygQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=eei5Xa8BTw6LAI6TXNS625+orPD6V13lyeMiZgT5sss=; b=b49tE2mbwP0gxgbhcfqb7JGdIVkYf1K1zWFH0XSlLPgnr/DSFpGa5qLRnBaNp6fx7B Fqz98iP0AHoJoKAWWOChRMpIO7yNPdBrC3lb85yF/poGAFkXejjnxyEZEODih9webUuc gicYyhw4Hln+ru1j3Rdu0AVyOo5s5+Yx2fHJLOPxktv072W984w6CHV1ew1WeFh/x5gD CwT2dP+2eubeqf2u00OM90+vldiPE4WxlsHaE8LHUkz+rge6FQYoHXtN/T4m/sPICGb7 4Ru7qPXq3Jx/OG1HNWd021rNWrEpj7p4CjmnZHGT6mymL6Gq+G6Tsyd7ab9dbt0fmYyB lELw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m55si6711345edc.17.2019.09.30.01.42.47; Mon, 30 Sep 2019 01:43:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730033AbfI3Imm (ORCPT + 99 others); Mon, 30 Sep 2019 04:42:42 -0400 Received: from mail105.syd.optusnet.com.au ([211.29.132.249]:35671 "EHLO mail105.syd.optusnet.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726121AbfI3Iml (ORCPT ); Mon, 30 Sep 2019 04:42:41 -0400 Received: from dread.disaster.area (pa49-181-226-196.pa.nsw.optusnet.com.au [49.181.226.196]) by mail105.syd.optusnet.com.au (Postfix) with ESMTPS id 1ED87362787; Mon, 30 Sep 2019 18:42:34 +1000 (AEST) Received: from dave by dread.disaster.area with local (Exim 4.92.2) (envelope-from ) id 1iErGL-0007Hh-Iu; Mon, 30 Sep 2019 18:42:33 +1000 Date: Mon, 30 Sep 2019 18:42:33 +1000 From: Dave Chinner To: Ira Weiny Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org, linux-mm@kvack.org, Jeff Layton , Jan Kara , Theodore Ts'o , John Hubbard , Dan Williams , Jason Gunthorpe Subject: Re: Lease semantic proposal Message-ID: <20190930084233.GO16973@dread.disaster.area> References: <20190923190853.GA3781@iweiny-DESK2.sc.intel.com> <20190923222620.GC16973@dread.disaster.area> <20190925234602.GB12748@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190925234602.GB12748@iweiny-DESK2.sc.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.2 cv=FNpr/6gs c=1 sm=1 tr=0 a=dRuLqZ1tmBNts2YiI0zFQg==:117 a=dRuLqZ1tmBNts2YiI0zFQg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=J70Eh1EUuV4A:10 a=7-415B0cAAAA:8 a=UEOKGneJplBUkCUAY6MA:9 a=CjuIK1q_8ugA:10 a=biEYGPWJfzWAr4FL6Ov7:22 Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Wed, Sep 25, 2019 at 04:46:03PM -0700, Ira Weiny wrote: > On Tue, Sep 24, 2019 at 08:26:20AM +1000, Dave Chinner wrote: > > Hence, AFIACT, the above definition of a F_RDLCK|F_LAYOUT lease > > doesn't appear to be compatible with the semantics required by > > existing users of layout leases. > > I disagree. Other than the addition of F_UNBREAK, I think this is consistent > with what is currently implemented. Also, by exporting all this to user space > we can now write tests for it independent of the RDMA pinning. The current usage of F_RDLCK | F_LAYOUT by the pNFS code allows layout changes to occur to the file while the layout lease is held. IOWs, your definition of F_RDLCK | F_LAYOUT not being allowed to change the is in direct contradition to existing users. I've said this several times over the past few months now: shared layout leases must allow layout modifications to be made. Only allowing an exclusive layout lease to modify the layout rules out many potential use cases for direct data placement and p2p DMA applications, not to mention conflicts with the existing pNFS usage. Layout leases need to support more than just RDMA, and tailoring the API to exactly the immediate needs of RDMA is just going to make it useless for anything else. I'm getting frustrated now because we still seem to be going around in circles and getting nowhere. Cheers, Dave. -- Dave Chinner david@fromorbit.com