From owner-freebsd-current Sun Mar 1 15:59:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28210 for freebsd-current-outgoing; Sun, 1 Mar 1998 15:59:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28189; Sun, 1 Mar 1998 15:58:59 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA03679; Sun, 1 Mar 1998 18:58:45 -0500 (EST) (envelope-from toor) Message-Id: <199803012358.SAA03679@dyson.iquest.net> Subject: Re: Lockup in inode/nfsrcv on loopback NFS mount In-Reply-To: from Brian Tao at "Mar 1, 98 06:19:50 pm" To: taob@nbc.netcom.ca (Brian Tao) Date: Sun, 1 Mar 1998 18:58:45 -0500 (EST) Cc: dyson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Tao said: > On Sun, 1 Mar 1998, John S. Dyson wrote: > > > > There has been a historical problem with NFSv3 hanging on localhost > > filesystems. Is this a possibility? If so, NFSv2 is a short-term > > answer (if it is fast enough for you.) > > Yep, NFSv2 works, but it creeps along very slowly. A dd never > seems to climb above about 400K/sec on a P100, regardless of the block > size. I notice a lot of hard drive chatter during any sustained write > operation. Anyway, I don't actually need loopback NFS mounts... it > was something I tried when tracking down another problem. > > Is it specifically a problem with the lo interface? Can it be > avoided by somehow going through an Ethernet driver? > I think that it is a deadlock mostly at the VFS/NFS level. Using the ethernet driver *might* give enough buffering, but I think that the deadlock is inevitable even in that case. As it is now, NFSv3 on a localhost (or any loopback) will likely be a problem. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message