From owner-cvs-all Fri Mar 14 10: 3:48 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E54937B401; Fri, 14 Mar 2003 10:03:44 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FD6E43FBD; Fri, 14 Mar 2003 10:03:42 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.8/8.12.8) with ESMTP id h2EI3Zjl008507; Fri, 14 Mar 2003 19:03:35 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.8/8.12.8/Submit) id h2EI3Zb0008506; Fri, 14 Mar 2003 19:03:35 +0100 (CET) Date: Fri, 14 Mar 2003 19:03:35 +0100 From: Wilko Bulte To: Poul-Henning Kamp Cc: "Daniel C. Sobral" , Garance A Drosihn , Juli Mallett , Eivind Eklund , Mike Silbersack , David Schultz , src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/vm ... SIGDANGER Message-ID: <20030314190335.A8491@freebie.xs4all.nl> References: <3E720D44.6010300@tcoip.com.br> <8023.1047662161@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8023.1047662161@critter.freebsd.dk>; from phk@phk.freebsd.dk on Fri, Mar 14, 2003 at 06:16:01PM +0100 X-OS: FreeBSD 4.8-RC X-PGP: finger wilko@freebsd.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Mar 14, 2003 at 06:16:01PM +0100, Poul-Henning Kamp wrote: > In message <3E720D44.6010300@tcoip.com.br>, "Daniel C. Sobral" writes: > >Poul-Henning Kamp wrote: > >> > >> * Fourth: A cheap syscall or sysctl which can be used to get a real-time > >> qualified answer to the simple question: Is the system short of RAM ? > >> > >> Many programs (directly or implicitly through the use of malloc(3)) > >> can adapt their behaviour, but lack the means to when to do that. > > > >That's a suggested use for SIGDANGER, actually. Still bad for the > >programs that get killed. :-) > > No, SIGDANGER is too heavy-handed, it only comes in when we run out > of RAM _and_ swap-space. > > I'm looking for something which tells me when we start to _use_ swap. Implement SIGWORRY? -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message