Re: [nfsv4] New version of sparse draft (draft-hildebrand-nfsv4-read-sparse-01.txt)
Dean Hildebrand <seattleplus@gmail.com> Fri, 01 October 2010 20:01 UTC
Return-Path: <seattleplus@gmail.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 7D3FF3A6E0E for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 13:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ZXBGPmSof0rh for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 13:01:37 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 0393A3A6E04 for <nfsv4@ietf.org>; Fri, 1 Oct 2010 13:01:36 -0700 (PDT)
Received: by iwn3 with SMTP id 3so5047059iwn.31 for <nfsv4@ietf.org>; Fri, 01 Oct 2010 13:02:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=Ra7hKk6zga6A44cpZRfLvhkXS9nNDjSFoDt7wjl7eRk=; b=QVVHpy0fC/ij3yObP4NiVREthDNPiCVI4o+NLLxGmffDC+atgJgIAqVD5FmAnFS+q3 ltIK6JvsnnD+PTG5OboFBiWiwf4tLSxacPPUL5Wn4U9ahFFlcXTqe/FGTVUruADOLX6o rag1qFYIqgQ7WwpKJx2TRAwiyiIMg2QbupXNE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=x9agbOkuApPPFPZkjOEFeCXUYDvxNLJJ7oPDuNMix5CMW0huX7+RCbizBjPf0+Bum8 tM1Boe2MNUXh8w8aAnlCPbErliq4y+sLoFDmgkjf1ujn/K6+m6dBWE4sp5yxPKP/+tZV qKz2s2XlRcdsLl6255HBJ+34zl/ul0/BTOA5c=
Received: by 10.231.31.135 with SMTP id y7mr6151730ibc.139.1285963345775; Fri, 01 Oct 2010 13:02:25 -0700 (PDT)
Received: from [192.168.1.43] (pool-71-112-128-104.sttlwa.dsl-w.verizon.net [71.112.128.104]) by mx.google.com with ESMTPS id h8sm1530516ibk.15.2010.10.01.13.02.19 (version=SSLv3 cipher=RC4-MD5); Fri, 01 Oct 2010 13:02:23 -0700 (PDT)
Message-ID: <4CA63E48.5070903@gmail.com>
Date: Fri, 01 Oct 2010 13:02:16 -0700
From: Dean Hildebrand <seattleplus@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Spencer Shepler <sshepler@microsoft.com>
References: <4CA3CE95.10407@gmail.com> <E043D9D8EE3B5743B8B174A814FD584F0A64D38F@TK5EX14MBXC124.redmond.corp.microsoft.com>
In-Reply-To: <E043D9D8EE3B5743B8B174A814FD584F0A64D38F@TK5EX14MBXC124.redmond.corp.microsoft.com>
Content-Type: multipart/alternative; boundary="------------000301030203060002020506"
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 20:01:38 -0000
On 10/1/2010 9:38 AM, Spencer Shepler wrote: > > Thanks for the update, Dean. > > I tend to agree with others that it is likely best to introduce a new > READ operation that > > incorporates the ideas presented in this draft. > While a new operation is simple, it puts all the onus on clients to call the correct function. Therefore, the only way for us to benefit from a new operation is if every client in existence stops using READ and switches to use the new operation. If they do that, then what's the point of having the READ operation at all? So with a new operation, I'm just not sure what the guidance to implementors would be? Stop using READ? We wanted a simple addition to the protocol, not to deprecate READ :) >This new operation could allow for ascatter/gather-like mechanism. Allowing the client to do a 1MB read and obtain all >of the data within that range while reducing the amount of data transferred is >attractive. > More generally, your draft does combine the idea of space allocated at > the server > > for the file with the method of effective transfer of data when zeros > or unallocated > > or uninitialized ranges exist. It is fine to combine the two ideas in > the draft but > > a little more explicit language would be helpful (I will make some > suggestions offline). > > It may be helpful to combine the these READ hole ideas with space > allocation > > controls provided to the client (allocate, release/trim, etc.). > Anyone else > > in the WG have an opinion here? > Yes, Bruce pointed out that my text switches between zero and unallocated. I need to clean up this language. But in fact, they are one and the same idea. The READ operation doesn't control space allocation, that would be create or write. The READ operation just wants to know if it should return data or a flag. 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. Dean > Spencer > > *From:* nfsv4-bounces@ietf.org [mailto:nfsv4-bounces@ietf.org] *On > Behalf Of *Dean Hildebrand > *Sent:* Wednesday, September 29, 2010 4:41 PM > *To:* nfsv4@ietf.org > *Subject:* [nfsv4] New version of sparse draft > (draft-hildebrand-nfsv4-read-sparse-01.txt) > > 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 > > Please have a look and give us any feedback. > > The main changes are: > 1) Added section regarding pNFS (which basically states that there are > no real changes to how pNFS works) > 2) Added example sparse read message flow > 3) Added statement to the effect that if a client sends a read request > for a chunk that ends in zeroes, the server can return a short read > (thanks to Benny) > 4) I didn't change the return value. There was a suggestion to use a > flag instead of overloaded the length parameter, but I'm not sure what > this gives us (although it might be more clear in the doc) > > Dean >
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- [nfsv4] New version of sparse draft (draft-hildeb… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… Matt W. Benjamin
- Re: [nfsv4] New version of sparse draft (draft-hi… Thomas Haynes
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… Thomas Haynes
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Benny Halevy
- [nfsv4] Fwd: Re: New version of sparse draft (dra… Benny Halevy
- Re: [nfsv4] New version of sparse draft (draft-hi… Benny Halevy
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Marc Eshel
- Re: [nfsv4] New version of sparse draft (draft-hi… david.noveck
- [nfsv4] Fwd: Re: New version of sparse draft (dra… Benny Halevy
- Re: [nfsv4] New version of sparse draft (draft-hi… Benny Halevy
- Re: [nfsv4] New version of sparse draft (draft-hi… david.noveck
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Spencer Shepler
- Re: [nfsv4] New version of sparse draft (draft-hi… Marc Eshel
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Spencer Shepler
- Re: [nfsv4] New version of sparse draft (draft-hi… Marc Eshel
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… Spencer Shepler
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft (draft-hi… Benny Halevy
- Re: [nfsv4] New version of sparse draft (draft-hi… Dean Hildebrand
- Re: [nfsv4] New version of sparse draft(draft-hil… Erasani, Pranoop
- Re: [nfsv4] New version of sparse draft(draft-hil… Matt W. Benjamin
- Re: [nfsv4] New version of sparsedraft(draft-hild… Erasani, Pranoop
- Re: [nfsv4] New version of sparse draft(draft-hil… J. Bruce Fields
- Re: [nfsv4] New version of sparse draft(draft-hil… Erasani, Pranoop
- Re: [nfsv4] New version of sparse draft (draft-hi… James Lentini
- Re: [nfsv4] New version of sparse draft(draft-hil… david.noveck
- Re: [nfsv4] New version of sparse draft(draft-hil… J. Bruce Fields