From owner-freebsd-current Tue Dec 9 13:22:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06650 for current-outgoing; Tue, 9 Dec 1997 13:22:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06639 for ; Tue, 9 Dec 1997 13:22:40 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id WAA01202; Tue, 9 Dec 1997 22:20:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Geoff Mohler cc: current@FreeBSD.ORG Subject: Re: Namei cache? In-reply-to: Your message of "Tue, 09 Dec 1997 14:14:16 CST." Date: Tue, 09 Dec 1997 22:20:23 +0100 Message-ID: <1200.881702423@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , Geoff Mohle r writes: >> In current there is little you can do. >> >> You can try to increase: >> >> kern.maxvnodes >> debug.wantfreevnodes > >I see what these values currently are, but what are my boundaries and >rules I have to follow in changing them..IE: stay in 4096 >incrememnts..dont go above 99999...etc. You'll run out of memory if you set them too high... Add 10% or so at a a time, let it run for a day before you judge the result... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."