From owner-freebsd-questions@FreeBSD.ORG Wed Apr 23 10:54:24 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E49E837B401 for ; Wed, 23 Apr 2003 10:54:24 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41F7F43F85 for ; Wed, 23 Apr 2003 10:54:24 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com[24.147.188.198]) by rwcrmhc51.attbi.com (rwcrmhc51) with ESMTP id <2003042317542305100196h8e>; Wed, 23 Apr 2003 17:54:23 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198] (may be forged)) by be-well.ilk.org (8.12.9/8.12.7) with ESMTP id h3NHsMoQ002130 for ; Wed, 23 Apr 2003 13:54:22 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h3NHsM6i002127; Wed, 23 Apr 2003 13:54:22 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: freebsd-questions@freebsd.org References: <20030422004530.CAAB.BLUEESKIMO@gmx.net> <3EA53661.6010007@potentialtech.com> <1051069331.88928.5.camel@jake> <3EA69B99.4030201@potentialtech.com> From: Lowell Gilbert Date: 23 Apr 2003 13:54:22 -0400 In-Reply-To: <3EA69B99.4030201@potentialtech.com> Message-ID: <44u1cpumk1.fsf@be-well.ilk.org> Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Strange networking behaviour (memory leak?) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2003 17:54:25 -0000 Bill Moran writes: > Adam wrote: > >>FreeBSD is pretty smart about memory. In the top display you see active, > >>inactive, cache, buffer, wired, and free memory. The memory that's actually > >>free is really the sum of inactive, buffer, cache, and free. The free > >>memory is free immediately, those other three can become free with very, > >>very little effort on the part of the kernel, but if you call up the same > >>application again and it's still in inactive memory, it'll start up quicker > >>than if it has to reload it from disk. > >>Free memory is wasted memory. > > Wow, thanks for the clarifications (and education). I actually very > > glad > > you explained this to me. You'll have to excuse my ignorance on some > > topics; my lack of experience is sometimes glaringly obvious. > > Don't worry about it. If you search the list archives, I think you'll see > me asking the same question a number of years ago, and getting a similarly > helpful answer. Which explains why this is in the FAQ... http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#TOP-FREEMEM