RE: [nfsv4] device IDs and stateids

Mike Eisler <email2mre-ietf@yahoo.com> Sun, 11 November 2007 20:01 UTC

Return-path: <nfsv4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrIzz-0007tw-0h; Sun, 11 Nov 2007 15:01:39 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrIzy-0007tr-9E for nfsv4@ietf.org; Sun, 11 Nov 2007 15:01:38 -0500
Received: from web38115.mail.mud.yahoo.com ([209.191.124.142]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IrIzx-0007j9-U2 for nfsv4@ietf.org; Sun, 11 Nov 2007 15:01:38 -0500
Received: (qmail 59353 invoked by uid 60001); 11 Nov 2007 20:01:37 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=n+/7BA6iX3UPD51uNJC/FzekGIKrQBxZ9NAsl2/fr8jGuQJOtx9GayCQxJqfjuE1V54QDxGRfhKizcZqGwsm1g7KWaCXTP8io5w7ZhtdjdKA3i+7/LVS+i4a6+Q2m4qxi9qSQJk0rgKxXydgjIp3xzlM+wqGRaPYfe5DVDexZGE=;
X-YMail-OSG: wA9ZOkMVM1lV_SxkBs_lthw41HSH0QANQEJ34d1Uzk_TfzyWwsBm7NR0yxDwI9DIeufIJw--
Received: from [198.95.226.230] by web38115.mail.mud.yahoo.com via HTTP; Sun, 11 Nov 2007 12:01:37 PST
Date: Sun, 11 Nov 2007 12:01:37 -0800
From: Mike Eisler <email2mre-ietf@yahoo.com>
Subject: RE: [nfsv4] device IDs and stateids
To: "Noveck, Dave" <Dave.Noveck@netapp.com>, Spencer Shepler <Spencer.Shepler@Sun.COM>
In-Reply-To: <C98692FD98048C41885E0B0FACD9DFB80567E961@exnane01.hq.netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <333459.57565.qm@web38115.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: nfsv4@ietf.org
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: email2mre-ietf@yahoo.com
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
Errors-To: nfsv4-bounces@ietf.org

--- "Noveck, Dave" <Dave.Noveck@netapp.com> wrote:


>  I think some of the confusion about
> cfh on GETDEVICEINFO and GETDEVICELIST  may be related to
> the fact that device stateis have been described as delegations
> on the mapping without being terribly clear on details of 
> that analogy/identification.

Before I go catch a bus, the cfh for GETDEVICE* is likely an
artificial construct by the server. No cfh is required on input to
to GETDEVICE*, but a cfh is generated. This cfh is used when
the client returns the device stateid (or if one of zillions of device
stateids if trends continue), and also on recall of the device
stateid(s).

We have a delegation and recall mechanism; we shouldn't implement
a parallel system that does the same thing.


_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4