From owner-freebsd-current Sun Apr 5 17:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00905 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:23:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wankers.net (root@host-32-96-40-98.atl.bellsouth.net [32.96.40.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00674; Sun, 5 Apr 1998 17:22:17 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id UAA08418; Sun, 5 Apr 1998 20:21:08 -0400 (EDT) (envelope-from dex@wankers.net) Date: Sun, 5 Apr 1998 20:21:07 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: "John S. Dyson" cc: dag-erli@ifi.uio.no, dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <199804060017.TAA01675@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oh...I was talking about top showing 104k, as opposed to swapinfo showing 40k. -Jon On Sun, 5 Apr 1998, John S. Dyson wrote: > > > > as you can see, top still reflects data cached in swap, but look at > > swapinfo: > > > > % swapinfo > > Device 1K-blocks Used Avail Capacity Type > > /dev/sd0b 262144 40 262040 0% Interleaved > > > > My interpretation, here, is that the data is still cached, but that space > > will be reused if I don't run GIMP again, but will stay cached in case I > > need it (OR there's a bug hidden somewhere). > > > What you are seeing is parts of other processes on swap. FreeBSD does > not gratuitiously swap unneeded pages back in only to free swap space > That swap allocation that you see could be part of init or some other > process that is still running. > > John > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message