Re: [nfsv4] [FedFS] Multiple FSL resolution

Nicolas Williams <Nicolas.Williams@sun.com> Mon, 14 December 2009 16:58 UTC

Return-Path: <Nicolas.Williams@sun.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 675B13A684D for <nfsv4@core3.amsl.com>; Mon, 14 Dec 2009 08:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level:
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[AWL=-0.641, BAYES_05=-1.11, HELO_MISMATCH_COM=0.553, 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 kWvIRbE-94wQ for <nfsv4@core3.amsl.com>; Mon, 14 Dec 2009 08:58:55 -0800 (PST)
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by core3.amsl.com (Postfix) with ESMTP id 70A3A3A6833 for <nfsv4@ietf.org>; Mon, 14 Dec 2009 08:58:55 -0800 (PST)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id nBEGwfLq026460 for <nfsv4@ietf.org>; Mon, 14 Dec 2009 16:58:41 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id nBEGwffU003426 for <nfsv4@ietf.org>; Mon, 14 Dec 2009 09:58:41 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id nBEGheuN004312; Mon, 14 Dec 2009 10:43:40 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id nBEGhbUS004311; Mon, 14 Dec 2009 10:43:37 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 14 Dec 2009 10:43:37 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: "Everhart, Craig" <Craig.Everhart@netapp.com>
Message-ID: <20091214164337.GK1516@Sun.COM>
References: <0F3F903BA6B4A54984787888AF6EA5C404671F46@CORPUSMX40A.corp.emc.com> <E7372E66F45B51429E249BF556CEFFBC0961A3AD@RTPMVEXC1-PRD.hq.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E7372E66F45B51429E249BF556CEFFBC0961A3AD@RTPMVEXC1-PRD.hq.netapp.com>
User-Agent: Mutt/1.5.7i
Cc: nfsv4@ietf.org, stacey_chris@emc.com
Subject: Re: [nfsv4] [FedFS] Multiple FSL resolution
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: Mon, 14 Dec 2009 16:58:56 -0000

On Thu, Dec 10, 2009 at 11:05:23AM -0500, Everhart, Craig wrote:
> As a quick shot, I believe that section 3.2, step 5, is in error, at
> least for the case of NFSv4{,.1}, which is the domain of discourse here.
> All the FSL's for a given FSN should be converted and sent to the file
> server client, and the client can choose among them.
> 
> There are possible opportunities for introduction of policy-controlled
> behavior if there are more FSL's than a given server can convert or than
> it can communicate to the file server client, but the idea is that the
> file servers take all locations from the NSDB and present them all to
> the client for its choice.

Indeed, you might not want the server to take too long resolving a
junction.  So if there's 10 FSLs the server might return as many as it
can resolve in, say, 10 seconds.

An implementation guideline should be included encouraging server
implementors to make junction resolution as parallel as possible.

Nico
--