Re: [nfsv4] question on bulk recall text

Benny Halevy <bhalevy@panasas.com> Tue, 12 October 2010 17:42 UTC

Return-Path: <bhalevy@panasas.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 104DE3A69D0 for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 10:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8y++o9g42mx3 for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 10:42:42 -0700 (PDT)
Received: from exprod5og108.obsmtp.com (exprod5og108.obsmtp.com [64.18.0.186]) by core3.amsl.com (Postfix) with SMTP id B76CC3A694D for <nfsv4@ietf.org>; Tue, 12 Oct 2010 10:42:41 -0700 (PDT)
Received: from source ([67.152.220.89]) by exprod5ob108.postini.com ([64.18.4.12]) with SMTP ID DSNKTLSeWnqvHf4tSNlGen8zs7mjiF533L9h@postini.com; Tue, 12 Oct 2010 10:43:56 PDT
Received: from lt.bhalevy.com ([172.17.3.222]) by daytona.int.panasas.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 Oct 2010 13:43:53 -0400
Message-ID: <4CB49E59.3040409@panasas.com>
Date: Tue, 12 Oct 2010 13:43:53 -0400
From: Benny Halevy <bhalevy@panasas.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Thunderbird/3.1.4
MIME-Version: 1.0
To: Trond Myklebust <Trond.Myklebust@netapp.com>
References: <AANLkTinx1ZQWko8D9XgmikaGAv4nHxoWJ2bDuM5O=y_u@mail.gmail.com> <1286902798.24878.9.camel@heimdal.trondhjem.org>
In-Reply-To: <1286902798.24878.9.camel@heimdal.trondhjem.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2010 17:43:54.0000 (UTC) FILETIME=[09C66900:01CB6A35]
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] question on bulk recall text
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: Tue, 12 Oct 2010 17:42:44 -0000

On 2010-10-12 12:59, Trond Myklebust wrote:
> On Tue, 2010-10-12 at 12:19 -0400, Fred Isaman wrote:
>> The text for bulk recalls in 12.5.5.2.1.5 seems flawed:
>>
>>    Once a CB_LAYOUTRECALL of LAYOUTRECALL4_ALL is sent, the server MUST
>>    NOT allow the client to use any layout stateid except for
>>    LAYOUTCOMMIT operations.  Once the client receives a CB_LAYOUTRECALL
>>    of LAYOUTRECALL4_ALL, it MUST NOT use any layout stateid except for
>>    LAYOUTCOMMIT operations.
>>
>> (similarly for LAYOUTRECALL4_FSID)
>>
>> My question: what stateid does the client use to send the required LAYOUTRETURN?
> 
> LAYOUTRETURN with a LAYOUTRETURN4_FSID or a LAYOUTRETURN4_ALL argument
> doesn't take a stateid. 

Right, but if the client wants to return individual layouts
in the process the question is still valid.
One reason to do that is to show progress while the client
is flushing its caches.

Benny

> 
> Cheers
>   Trond
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4