Date: Fri, 14 Mar 2003 11:31:56 -0600 From: Juli Mallett <jmallett@FreeBSD.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: "Daniel C. Sobral" <dcs@tcoip.com.br>, Garance A Drosihn <drosih@rpi.edu>, 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: <20030314113156.A10909@FreeBSD.org> In-Reply-To: <7901.1047661770@critter.freebsd.dk>; from phk@phk.freebsd.dk on Fri, Mar 14, 2003 at 06:09:30PM %2B0100 References: <3E720B5B.8090200@tcoip.com.br> <7901.1047661770@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: Poul-Henning Kamp <phk@phk.freebsd.dk> [ Data: 2003-03-14 ] [ Subjecte: Re: cvs commit: src/sys/vm ... SIGDANGER ] > >* Third, a sysctl to prevent overcommitting. With this on, memory would > >be always immediatly allocated, instead of on-demand. With this, no > >application would ever be killed. Either it aborted because it couldn't > >allocate more memory, or it didn't. Since this can lock out users from a > >machine, some of those that implemented this had a sort of reserve for > >an interactive root process (which could still get exhausted, but whatever). > > * 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. I'd love to see this, and I imagine adding something just enough to facilitate 'if (system_is_swapping)' might be fairly easy. Do you have a diff? -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; 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?20030314113156.A10909>