Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!rwwa.com!not-for-mail From: witr@rwwa.com (Robert Withrow) Newsgroups: comp.os.386bsd.development Subject: Re: Notes on the *new* FreeBSD V1.1 VM system Date: 23 Feb 1994 11:55:01 -0500 Organization: R.W. Withrow Associates Lines: 16 Message-ID: <2kg1p5$t01@meatball.rwwa.com> References: <BcxpGux.dysonj@delphi.com> <MYCROFT.94Feb20102534@duality.gnu.ai.mit.edu> <CLL9J6.FCF@endicor.com> <2ke3ss$l0d@u.cc.utah.edu> <Ja4p+zR.dysonj@delphi.com> Reply-To: witr@rwwa.com NNTP-Posting-Host: meatball.rwwa.com In article <Ja4p+zR.dysonj@delphi.com>, John Dyson <dysonj@delphi.com> writes: |> Terry Lambert <terry@cs.weber.edu> writes: |> |> >Personally, I think you should be required to rebuild a kernel with |> >"option FAST_AND_LOOSE" if you want overcommit enabled. |> |> We have not met, so this is meant in the best of humor.... |> hows about "option TIGHT_AND_STINGY" if you want overcommit disabled :-)). Or what about a syscall that says ``I want this process to have its swapspace guaranteed, here is my credit card number''. That would suit the database backends and their ilk, without gutting the statistical compromize of overcommiting. -- Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA