From owner-freebsd-arch@FreeBSD.ORG Sat Aug 2 07:20:42 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C994837B401 for ; Sat, 2 Aug 2003 07:20:42 -0700 (PDT) Received: from franky.speednet.com.au (franky.speednet.com.au [203.57.65.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F32843F75 for ; Sat, 2 Aug 2003 07:20:41 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au [203.38.96.242])h72EKcDs004245; Sun, 3 Aug 2003 00:20:39 +1000 (EST) (envelope-from andyf@speednet.com.au) Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au [172.22.2.1])h72EKbHT041542; Sun, 3 Aug 2003 00:20:37 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Sun, 3 Aug 2003 00:20:37 +1000 (EST) From: Andy Farkas X-X-Sender: andyf@hewey.af.speednet.com.au To: Poul-Henning Kamp In-Reply-To: <10603.1059832005@critter.freebsd.dk> Message-ID: <20030802235543.N41132-100000@hewey.af.speednet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: arch@freebsd.org Subject: Re: headsup: swap_pager.c X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2003 14:20:43 -0000 Poul-Henning Kamp wrote: > >You say > >"bogo-vnode". Please explain what that means. > > A bogos vnode. More would've been nice. > >What does "in a pinch" mean?? > > That for instance you are running out of swap, if NSWAPDEV==1 you cannot > add another swapdev because the one and only slot is occupied (and the > device is filled too). "running out of swap" is a situation I was *not* in, yet my system was totally unresponsive because it was continuously swapping. The physical disk could not keep up with page-in demand. How am I supposed to magically "add" another [physical] disk while the box is spasticly trying to swap around a 200M plus working-set into 32M physical RAM. When you're box starts swapping (in *my* experience) your box is fsck'd. All I'm saying is that whatever you do with the code (and I don't give a fsck what happens to it) it aint gonna fix, or change, anything. You are wasting your time. And no, i'm not telling you what or how to code. > >What do those numbers in kern.malloc mean?? > > That the corresponding amount of RAM is unchangably occupied by a table > which is 3/4 empty and therefore nothing else can use that RAM productively. # sysctl kern.malloc | grep -i swap SWAP 2 73K 137K 12 64,65536 Again, more explaining would be good. "corresponding amount of RAM" [you must mean the 73K and 173K values] "unchangably occupied" [my values change as I add and remove swap devices] "by a table which is 3/4 empty" [fixed by specifying NSWAPDEV=1] Please, bash me more...I still dont understand why you are trying to fix unbroken code... yes, I feel very alone in my crusade... -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/