Date: Tue, 13 Jul 1999 19:25:10 -0700 From: David Greenman <dg@root.com> To: "Charles M. Hannum" <root@ihack.net> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Noriyuki Soda <soda@sra.co.jp>, Jason Thorpe <thorpej@nas.nasa.gov>, "Brian F. Feldman" <green@FreeBSD.ORG>, bright@rush.net, dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, jon@oaktree.co.uk, tech-userlevel@netbsd.org Subject: Re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) Message-ID: <199907140225.TAA14312@implode.root.com> In-Reply-To: Your message of "Tue, 13 Jul 1999 21:55:01 EDT." <199907140155.VAA14113@bikini.ihack.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>The point is, the OS should have provided *some* mechanism to insure >that the long-running process wasn't affected. It didn't. That's a >clear failure of the OS to provide a reasonable environment for this >type of computing. > >Whether this should be solved by switching to a no-overcommit policy, >fiddling with the overcommit policy in some way, or whatever, is a >different issue. But you have not yet proposed any mechanism that >would have prevented this problem while still permitting me to get >work done. I've long felt that the best solution to problems like this is a per-user swap space quota. This gives admins a knob to manage the allocation of swap space while still allowing overcommit. The downside is that it doesn't provide a graceful way for a program to recover from it's overconsumption sins. I'd argue, however, that buggy software or incorrectly tuned systems should get what they deserve. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907140225.TAA14312>