IETF Logo Mail Archive

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

"J. Bruce Fields" <bfields@fieldses.org> Fri, 01 October 2010 21:32 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 78D373A6BB0 for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 14:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level:
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.006, 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 COFiiTq9K6f8 for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 14:32:39 -0700 (PDT)
Received: from fieldses.org (fieldses.org [174.143.236.118]) by core3.amsl.com (Postfix) with ESMTP id 930933A6B4E for <nfsv4@ietf.org>; Fri, 1 Oct 2010 14:32:39 -0700 (PDT)
Received: from bfields by fieldses.org with local (Exim 4.71) (envelope-from <bfields@fieldses.org>) id 1P1nE9-0002J3-7r; Fri, 01 Oct 2010 17:33:13 -0400
Date: Fri, 01 Oct 2010 17:33:13 -0400
To: Dean Hildebrand <seattleplus@gmail.com>
Message-ID: <20101001213313.GD1472@fieldses.org>
References: <4CA3CE95.10407@gmail.com> <E043D9D8EE3B5743B8B174A814FD584F0A64D38F@TK5EX14MBXC124.redmond.corp.microsoft.com> <4CA63E48.5070903@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4CA63E48.5070903@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 21:32:41 -0000

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.

--b.

v2.23.0 | Report a Bug | By Email