From owner-freebsd-current Sun Apr 5 14:36:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19904 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:36:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19856; Sun, 5 Apr 1998 14:36:06 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA00680; Sun, 5 Apr 1998 16:35:53 -0500 (EST) (envelope-from toor) Message-Id: <199804052135.QAA00680@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <3.0.5.32.19980405172640.00915e30@mail.kersur.net> from Dan Swartzendruber at "Apr 5, 98 05:26:40 pm" To: dswartz@druber.com (Dan Swartzendruber) Date: Sun, 5 Apr 1998 16:35:53 -0500 (EST) Cc: dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Swartzendruber said: > > My only quibble with this technique is that it would seem to make it > harder to tell if your machine is really running low on swap or not > (e.g. swap as backing store for stack/heap/whatever *is* critical and > allocation failure can cause application failure, whereas swap being > used to cache random cruft is in the "who really cares" department). > Or is there some way to tell the difference? > It is difficult not only to tell if you are low on swap, but also it is hard to quantify being low on memory. I have been thinking about this over the last year or so. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message