From owner-freebsd-fs@FreeBSD.ORG Mon Dec 3 01:27:33 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 2DD8061A for ; Mon, 3 Dec 2012 01:27:33 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id D026E8FC0C for ; Mon, 3 Dec 2012 01:27:32 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAJH/u1CDaFvO/2dsb2JhbABEFoYWuXNzgh4BAQMlVhsOCgICDRkCX4gjDKwmkVuBIosegy6BEwOIXo0jgRyPK4MQggM X-IronPort-AV: E=Sophos;i="4.84,202,1355115600"; d="scan'208";a="2792191" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 02 Dec 2012 20:27:25 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id ABFAEB3F47; Sun, 2 Dec 2012 20:27:25 -0500 (EST) Date: Sun, 2 Dec 2012 20:27:25 -0500 (EST) From: Rick Macklem To: Konstantin Belousov Message-ID: <1751068041.1071962.1354498045662.JavaMail.root@erie.cs.uoguelph.ca> 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.201] 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: Mon, 03 Dec 2012 01:27:33 -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 ? Well, there is now a patch at: http://people.freebsd.org/~rmacklem/nfsv4.1.patch It is just under 7,000lines, so you may not want to look at it, but whatever you can do with it would be appreciated, rick