Re: [nfsv4] More layout stuff: layout return on close

Trond Myklebust <Trond.Myklebust@netapp.com> Wed, 24 November 2010 14:55 UTC

Return-Path: <Trond.Myklebust@netapp.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E3EF28C10D for <nfsv4@core3.amsl.com>; Wed, 24 Nov 2010 06:55:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nNyrvxDtsYr5 for <nfsv4@core3.amsl.com>; Wed, 24 Nov 2010 06:55:42 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 882F73A6A70 for <nfsv4@ietf.org>; Wed, 24 Nov 2010 06:55:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.59,248,1288594800"; d="scan'208";a="486578144"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 24 Nov 2010 06:56:34 -0800
Received: from svlrsexc2-prd.hq.netapp.com (svlrsexc2-prd.hq.netapp.com [10.57.115.31]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id oAOEuX9S008164; Wed, 24 Nov 2010 06:56:33 -0800 (PST)
Received: from SACMVEXC2-PRD.hq.netapp.com ([10.99.115.17]) by svlrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Nov 2010 06:56:33 -0800
Received: from 10.58.53.62 ([10.58.53.62]) by SACMVEXC2-PRD.hq.netapp.com ([10.99.115.16]) with Microsoft Exchange Server HTTP-DAV ; Wed, 24 Nov 2010 14:56:32 +0000
Received: from heimdal.trondhjem.org by SACMVEXC2-PRD.hq.netapp.com; 24 Nov 2010 09:56:32 -0500
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
In-Reply-To: <4CECE104.5080009@desy.de>
References: <1290552459.30508.4.camel@heimdal.trondhjem.org> <4CECC382.5020207@panasas.com> <4CECE104.5080009@desy.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Organization: NetApp Inc
Date: Wed, 24 Nov 2010 09:56:31 -0500
Message-ID: <1290610592.3234.20.camel@heimdal.trondhjem.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 (2.32.1-1.fc14)
X-OriginalArrivalTime: 24 Nov 2010 14:56:33.0238 (UTC) FILETIME=[C8C6F760:01CB8BE7]
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] More layout stuff: layout return on close
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Nov 2010 14:55:46 -0000

On Wed, 2010-11-24 at 10:55 +0100, Tigran Mkrtchyan wrote:
>  
> We are in a quite weird situation here. From one side servers asks  a
> client to return
> layout on close, but from other side you have to keep track of the
> layout and recall it to
> ensure that the client will not use it any more.  I would love to see
> this part of the spec to
> be more deterministic. But it we change it not to be a more strong
> requirements, then
> some of the current clients will become not complaint with the spec. Are
> we ok with that?

I fail to see your point. Which clients would become spec incompliant if
we relax the requirement that they must send a layoutreturn before close
when the server sets the logr_return_on_close flag? Relaxing a
requirement is not equivalent to prohibiting the behaviour.

> And of course I have to change layout handling in our server we rely on
> layoutreturn. Which
> is not a big change (I think). BTW, is there any other server uses
> return_on_close ?

You don't have to change the server, but if you don't then it will
perform less than optimally with forgetful clients.


Trond
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com