Date: Fri, 14 Mar 2003 15:05:16 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>, "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: 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: <p05200f2bba97e5a92150@[128.113.24.47]> In-Reply-To: <8023.1047662161@critter.freebsd.dk> References: <8023.1047662161@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
At 6:16 PM +0100 3/14/03, 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 ? > > > > 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. The web page I gave in my other message also talks about a 'psdanger' routine, which sounds like it might be what you're talking about. [of course, as a userland-type-of-programmer, I'm hoping some kernel-type will get excited about the idea and implement the same set of ideas for FreeBSD. :-)] -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu 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?p05200f2bba97e5a92150>