Date: Fri, 14 Mar 2003 19:03:35 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: "Daniel C. Sobral" <dcs@tcoip.com.br>, 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: <20030314190335.A8491@freebie.xs4all.nl> In-Reply-To: <8023.1047662161@critter.freebsd.dk>; from phk@phk.freebsd.dk on Fri, Mar 14, 2003 at 06:16:01PM %2B0100 References: <3E720D44.6010300@tcoip.com.br> <8023.1047662161@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030314190335.A8491>