Re: [nfsv4] New version of sparse draft (draft-hildebrand-nfsv4-read-sparse-01.txt)

"J. Bruce Fields" <bfields@fieldses.org> Fri, 01 October 2010 14:36 UTC

Return-Path: <bfields@fieldses.org>
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 B6FB83A6EEB for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 07:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599]
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 aFioywcnAlH4 for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 07:36:57 -0700 (PDT)
Received: from fieldses.org (fieldses.org [174.143.236.118]) by core3.amsl.com (Postfix) with ESMTP id D27713A6F5B for <nfsv4@ietf.org>; Fri, 1 Oct 2010 07:36:49 -0700 (PDT)
Received: from bfields by fieldses.org with local (Exim 4.71) (envelope-from <bfields@fieldses.org>) id 1P1gic-0006Xb-Fm; Fri, 01 Oct 2010 10:36:14 -0400
Date: Fri, 01 Oct 2010 10:36:14 -0400
To: Dean Hildebrand <seattleplus@gmail.com>
Message-ID: <20101001143614.GB17310@fieldses.org>
References: <4CA3CE95.10407@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4CA3CE95.10407@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
From: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] New version of sparse draft (draft-hildebrand-nfsv4-read-sparse-01.txt)
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: Fri, 01 Oct 2010 14:36:58 -0000

On Wed, Sep 29, 2010 at 04:41:09PM -0700, Dean Hildebrand wrote:
>  Hello,
> 
> I uploaded a new version of our internet draft "Simple and Efficient
> Read Support for Sparse Files".
> 
> http://www.ietf.org/id/draft-hildebrand-nfsv4-read-sparse-01.txt

A couple other points:

	- By returning an error in a situation that isn't really an
	  error, we abort processing the compound when we don't really
	  need to.  I suppose we could make a special exceptions for
	  NFS4ERR_HOLE, but, yuch.
	- The server can't return NFS4ERR_HOLE unless it knows the
	  client is prepared to handle it.  One solution would be to
	  make client support for NFS4ERR_HOLE mandatory in whichever
	  minor version we add sparse-read support.  Whether that works
	  well may depend on the eventual size of the minor version.
	  It's easier if people can increment new features
	  incrementally.

--b.