From owner-freebsd-current Fri Feb 28 20:12:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA07944 for current-outgoing; Fri, 28 Feb 1997 20:12:06 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07914 for ; Fri, 28 Feb 1997 20:12:02 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id EAA16196; Sat, 1 Mar 1997 04:11:54 GMT Date: Sat, 1 Mar 1997 13:11:54 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/conf options In-Reply-To: <199702282247.PAA02481@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Feb 1997, Terry Lambert wrote: > It's silly to think you can have "too many vnodes"... what resource > that is usable are you preventing starving by hard limiting them? > How do you run a program to take advantage of the resource you > "saved" this way, if the program you want to run won't run because > you are out of vnodes? ...Silly. It's a non-decreasing pool of memory, some might want a limit on it's growth so that currently running processes and other kernel functions aren't negatively affected. Having a non-decreasing pool makes it a little less complicated in the fs code. You only need to worry about the validity of the contents of a vp and not the validity of the vp itself. The code is complicated as it is, have you looked at the lite2 stuff? Whew, I feel like we need something like SUN's lint_lock aka. warlock. NOTE(LOCK_RELEASED_AS_A_SIDE_EFFECT); The boundaries between a consistent state and an inconsistent state are pretty tough to follow. Regards, Mike Hancock