[nfsv4] parallel LAYOUTGETs using open stateid

Fred Isaman <iisaman@citi.umich.edu> Thu, 07 October 2010 13:20 UTC

Return-Path: <faisaman4@gmail.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 1882B3A6F33 for <nfsv4@core3.amsl.com>; Thu, 7 Oct 2010 06:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id jtWnScZ-xHIa for <nfsv4@core3.amsl.com>; Thu, 7 Oct 2010 06:20:17 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com []) by core3.amsl.com (Postfix) with ESMTP id 0D7153A6E5E for <nfsv4@ietf.org>; Thu, 7 Oct 2010 06:20:16 -0700 (PDT)
Received: by bwz9 with SMTP id 9so537120bwz.31 for <nfsv4@ietf.org>; Thu, 07 Oct 2010 06:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=n8agxltmDR7sLDQmLBsBeAGElg53yi2u0RMF4zkNTdk=; b=U1bd6kUvIIkSqmKpx9UVOT1oWlFFwaHwwnWCrAnn8cUGTWFONGZvS6famuc0iz058M HybJ/foDO49z56DFfPtDsNSdoQDX4a+H5s7lN9APSf5VsZrqoWeBDnZXMACksaQwMCmI +2CJcS6Wm/AQFhmixrcjk/A2foivEVvRUlZUA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=gDwXjYxFYp08lVJtcIw2VdNyN2Dv6HGQd7cr/TvjOfUUsFAaSeFoei7eioUx2lTweZ 6Kd75M7eU4LoEmJ5G48/adwoaa39VRkOMgNTYG2tyOiZCzg2fLRfVvmE1SgkmGwrQobx JMUXfmGVDRCt3AmVJLgbIf5fzE/rf8r034FGY=
MIME-Version: 1.0
Received: by with SMTP id h20mr651501bkl.186.1286457678634; Thu, 07 Oct 2010 06:21:18 -0700 (PDT)
Sender: faisaman4@gmail.com
Received: by with HTTP; Thu, 7 Oct 2010 06:21:18 -0700 (PDT)
Date: Thu, 07 Oct 2010 09:21:18 -0400
X-Google-Sender-Auth: KiHd5jwalGdm7wtwwlYKeYW0STE
Message-ID: <AANLkTinZ1t1YbL55vkT0OJ0i2j9AqNuvFStTwFoGO-dB@mail.gmail.com>
From: Fred Isaman <iisaman@citi.umich.edu>
To: nfsv4@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [nfsv4] parallel LAYOUTGETs using open stateid
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: Thu, 07 Oct 2010 13:20:18 -0000

This question came up as I was going through our layout stateid code.

Can the client send multiple LAYOUTGETs in parallel before getting a
layoutstateid by using an open stateid?
If so, what is the server response?  The spec is not clear, but I
would assume it would do one of:
a) returning an error (what error?) on all but the first LAYOUTGET it sees
b) matching the openstateid to the layoutstateid it has already given
out and sending a reply with that stateid and a bumped seqid