Date: Fri, 14 Mar 2003 18:16:01 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: Garance A Drosihn <drosih@rpi.edu>, Juli Mallett <jmallett@FreeBSD.org>, Eivind Eklund <eivind@FreeBSD.org>, Mike Silbersack <silby@silby.com>, David Schultz <das@FreeBSD.org>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/vm ... SIGDANGER Message-ID: <8023.1047662161@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 14 Mar 2003 14:11:32 -0300." <3E720D44.6010300@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-src" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8023.1047662161>