From owner-freebsd-current Tue Oct 20 01:03:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19998 for freebsd-current-outgoing; Tue, 20 Oct 1998 01:03:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19993 for ; Tue, 20 Oct 1998 01:03:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA18145; Tue, 20 Oct 1998 09:01:26 +0100 (BST) Date: Tue, 20 Oct 1998 09:01:26 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: Mark Mayo , mike@smith.net.au, dg@root.com, green@zone.syracuse.NET, grog@lemis.com, julian@whistle.com, bag@sinbin.demos.su, rock@cs.uni-sb.de, current@FreeBSD.ORG Subject: Re: -current NFS problem In-Reply-To: <199810200000.RAA19037@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Oct 1998, Terry Lambert wrote: > > > > Has anyone asked Rick Macklem about this? > > > > > > Rick bowed out of the NFS game a long time ago. Kirk would be a better > > > bet. > > [ ... ] > > > In general, he's not interested in helping FreeBSD in any way, since > > he thinks the code has become too "polluted" and "complicated" now. > > (which I would disagree with.. initial inspection by myself a while > > ago suggested that not much at all has really changed..) > > I'd agree with him, starting with the "cookie" for VOP_READDIR. Which was also in Lite2. > > > > As for any other help, as I said, give me a list of specific questions > > and I'll do my best to get answers. > > I think if we get one shot at this, the list of questions should be > agreed upon. > > My main question would be: > > o Do you see any reason why nfsnode locking should be necessary? The last time I spoke to Rick about this, he said that the reason NFS can't use a vnode lock is to prevent a server hang from causing a lock cascade ending up with the root vnode being locked and the whole machine wedged. I experimented for a while with a gross hack which only locked regular files but it was too complicated and I ditched it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message