From owner-freebsd-arch@FreeBSD.ORG Fri Mar 20 15:58:33 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36992106566C; Fri, 20 Mar 2009 15:58:33 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from skerryvore.cs.uoguelph.ca (skerryvore.cs.uoguelph.ca [131.104.94.204]) by mx1.freebsd.org (Postfix) with ESMTP id 9BCB68FC0C; Fri, 20 Mar 2009 15:58:32 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by skerryvore.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id n2KFwVfV007833; Fri, 20 Mar 2009 11:58:31 -0400 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n2KG3vv25648; Fri, 20 Mar 2009 12:03:57 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 20 Mar 2009 12:03:57 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Zachary Loafman In-Reply-To: <20090319164251.GA13081@zloafman.west.isilon.com> Message-ID: References: <20090315205229.GV55200@elvis.mu.org> <20090319164251.GA13081@zloafman.west.isilon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.94.204 Cc: Alfred Perlstein , freebsd-arch@freebsd.org Subject: Re: NFS version 4.0 for FreeBSD-CURRENT X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 15:58:33 -0000 On Thu, 19 Mar 2009, Zachary Loafman wrote: [good stuff snipped] > > I don't know if that affects the timing on this being merged to CURRENT > or not. It might be nice if we had an opportunity to review some things > prior to APIs/VOPs being set in stone, but it would also be nice to get > wider exposure for Rick's code. > Other than the va_filerev/i_modrev issue already mentioned (btw, I grep'd /usr/src and nothing uses va_filerev outside the kernel, it seems), I realized there is another API/VOP issue (kinda in the trivial category, but I should mention it). FreeBSD-CURRENT is out of bits for mnt_flag (the last spare one is used by Edward's ACL code) and it would be nice to add a couple of MNT_EXxxx flags for things like enabling/disabling delegations. Two obvious possible solutions: 1 - bump mnt_flag up to 64 bits 2 - create a separate mnt_exflag field [more stuff snipped] > > I think v4.1 is closer than you might think. We've received numerous > requests for pNFS, and I think many vendors will ship basic 4.1 stacks > this year. > I emailed a request for "predictions" about this on nfsv4@linux-nfs.org and I've only gotten one response sofar: [Tom Haynes wrote] Subject: Re: nfsv4.1 timeframe Rick Macklem wrote: > Anyone feel like making a prediction? (Ideally somewhat realistic:-) > Next year sounds more realistic based on what I saw at Connectathon. I'll post more responses if I get them, rick