From owner-svn-src-all@FreeBSD.ORG Thu May 5 16:42:25 2011 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C996106566C; Thu, 5 May 2011 16:42:25 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 143378FC12; Thu, 5 May 2011 16:42:24 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 407C51FFC35; Thu, 5 May 2011 16:42:23 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 10013845CA; Thu, 5 May 2011 18:42:23 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Rick Macklem References: <942285768.1045464.1304603653229.JavaMail.root@erie.cs.uoguelph.ca> Date: Thu, 05 May 2011 18:42:22 +0200 In-Reply-To: <942285768.1045464.1304603653229.JavaMail.root@erie.cs.uoguelph.ca> (Rick Macklem's message of "Thu, 5 May 2011 09:54:13 -0400 (EDT)") Message-ID: <86r58dqett.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: svn-src-head@freebsd.org, Rick Macklem , svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r221124 - in head: . sbin/mount sbin/mount_nfs sys/amd64/conf sys/fs/nfsclient sys/i386/conf sys/ia64/conf sys/nfsclient sys/pc98/conf sys/powerpc/conf sys/sparc64/conf sys/sun4v/conf X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2011 16:42:25 -0000 Rick Macklem writes: > Well, another way it could be handled would be to put the sysctls and > the global variables they manipulate in a module shared by both clients, > like sys/nfs/nfs_lock.c (module "nfslock"). Then the same sysctl would > affect both clients. (I hesitate to create "yet another" module just > to share the sysctls, but since "nfslock" is used by both clients, it > should work ok, I think.) I don't understand why you would want to do that. Can't you just change "oldnfs" back to "nfs" in the old stack? Hmm, it occurred to me that there is currently no way to tell the kernel that two drivers conflict with eachother. Perhaps I should take a shot at implementing a DRIVER_CONFLICT macro to mirror DRIVER_DEPEND. BTW, don't take this personally, I'm very grateful for (and impressed with) your NFS work, other than this little nit :) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no