From owner-freebsd-stable Sun Apr 5 13:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04475 for freebsd-stable-outgoing; Sun, 5 Apr 1998 13:23:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04423; Sun, 5 Apr 1998 13:23:33 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA11264; Sun, 5 Apr 1998 13:22:34 -0700 (PDT) Message-Id: <199804052022.NAA11264@implode.root.com> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-reply-to: Your message of "05 Apr 1998 18:13:06 +0200." From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Apr 1998 13:22:34 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >while. It's simply a *lot* faster to keep already-linked executables >in memory (and move them into swap when memory goes full) rather than >throwing them out and having to reload and relink them next time they >are invoked, as long as they haven't changed in the meantime. > >David, I hope my explanation is not too far off? Actually, it's not that the system has to do any re-linking. The reason that swap space is consumed even when you have plenty of memory is that the system also tries to cache regular file data, so freeing up memory for that by moving modified but not recently used process pages to swap is usually a good thing. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message