IETF Logo Mail Archive

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

James Lentini <jlentini@netapp.com> Sun, 03 October 2010 15:52 UTC

Return-Path: <jlentini@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 6B0843A6D5C for <nfsv4@core3.amsl.com>; Sun, 3 Oct 2010 08:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.844
X-Spam-Level:
X-Spam-Status: No, score=-5.844 tagged_above=-999 required=5 tests=[AWL=0.755, 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 y92UAGZhQ-uE for <nfsv4@core3.amsl.com>; Sun, 3 Oct 2010 08:52:51 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id C2A683A6D4D for <nfsv4@ietf.org>; Sun, 3 Oct 2010 08:52:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,275,1283756400"; d="scan'208";a="462209831"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 03 Oct 2010 08:53:30 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o93FrRsq014968; Sun, 3 Oct 2010 08:53:28 -0700 (PDT)
Date: Sun, 03 Oct 2010 11:53:27 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: "J. Bruce Fields" <bfields@fieldses.org>
In-Reply-To: <20101001213313.GD1472@fieldses.org>
Message-ID: <alpine.LFD.2.00.1010031149590.10194@jlentini-linux.nane.netapp.com>
References: <4CA3CE95.10407@gmail.com> <E043D9D8EE3B5743B8B174A814FD584F0A64D38F@TK5EX14MBXC124.redmond.corp.microsoft.com> <4CA63E48.5070903@gmail.com> <20101001213313.GD1472@fieldses.org>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: Deepak Kenchammana <kencham@netapp.com>, Michael Eisler <mre@netapp.com>, "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: Sun, 03 Oct 2010 15:52:53 -0000

On Fri, 1 Oct 2010, J. Bruce Fields wrote:

> On Fri, Oct 01, 2010 at 01:02:16PM -0700, Dean Hildebrand wrote:
> > We want to propose the FADVISE like operation mentioned in Mike's
> > draft at some point, this might be a good place for space allocation
> > information.
> 
> It would be trivial to specify a WRITEZ that could also take zero
> extents (so your write data could describe a range of zeroes instead of
> explicitly listing all the zeroes).
> 
> And then it would be up to the server whether to translate that into
> zero-writes or hole-punching, and in either case you could save some
> bandwidth.
> 
> That's a bit different from fadvise as I understand it.
> 
> I'm not suggesting you need to include a WRITEZ, just saying that on the
> write side also, transferring zeroes efficiently and allocating files
> are two different things.

WRITEZ sounds just like the HOLE_PUNCH operation described here:

http://tools.ietf.org/html/draft-iyer-nfsv4-space-reservation-ops-01

v2.27.6 | Report a Bug | By Email | System Status