From owner-freebsd-fs@FreeBSD.ORG Sun Nov 18 00:01:41 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8846A1E for ; Sun, 18 Nov 2012 00:01:41 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 9A54D8FC0C for ; Sun, 18 Nov 2012 00:01:40 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EABAkqFCDaFvO/2dsb2JhbABFhiC+F4IeAQEDAiNWGw4KAgINGQJZBoggC6x8kX6BIosSg3qBEwOIWo0ikEODDYF7 X-IronPort-AV: E=Sophos;i="4.83,270,1352091600"; d="scan'208";a="711640" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 17 Nov 2012 19:01:33 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 78992B403F; Sat, 17 Nov 2012 19:01:33 -0500 (EST) Date: Sat, 17 Nov 2012 19:01:33 -0500 (EST) From: Rick Macklem To: Konstantin Belousov Message-ID: <1913501733.497510.1353196893436.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20121117140448.GP73505@kib.kiev.ua> Subject: Re: RFC: moving NFSv4.1 client from projects to head MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 00:01:42 -0000 Konstantin Belousov wrote: > On Fri, Nov 16, 2012 at 09:15:49PM -0500, Rick Macklem wrote: > > Hi, > > > > I've been working on NFSv4.1 client support for FreeBSD > > for some time now and known issues from testing at a > > Bakeathon last June have been resolved. The patch is > > rather big, but I believe it should not affect the > > client unless the new mount options: > > minorversion=1,pnfs > > are used for an nfsv4 mount. > > > > Since I don't believe that the new NFS client will be > > affected unless these new mount options are used, I think > > it could go into head now. On the other hand, there are few > > NFSv4.1 servers currently available, so it might not yet > > be widely useful. (See below for slides w.r.t. server availability.) > > > > How do folks feel about doing this in early December? > > > > Since it doesn't change any KBIs, it could also be MFC'd > > to stable/9. Would MFC'ing it to stable/9 make sense? > > > > For those interested in testing and/or reviewing it, > > the code is currently in: > > base/projects/nfsv4.1-client > > (It is purely a kernel patch.) > > Also, the current state of NFSv4.1 servers is roughly: > > http://www.pnfs.com/docs/LISA-11-pNFS-BoF-final.pdf > > > > Thanks in advance for any comments, rick > IMO, the earlier the change that you feel mature enough, hits the HEAD > in > the HEAD x.0 cycle, the better. That said, would you mind to put a > diff > somewhere to ease the review and testing ? Will do, as soon as I get home at the end of Nov. (I can't do svn or uploads until then.) Thanks for the comments, rick