Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!enews.sgi.com!arclight.uoregon.edu!super.zippo.com!zdc!szdc!szdc-e!news From: "John S. Dyson" <dyson@freebsd.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD 2.1.x and Virtual Memory (VM) limits Date: Sun, 20 Oct 1996 22:10:54 -0500 Organization: John S. Dyson's home machine Lines: 31 Message-ID: <326AE9BE.41C67EA6@freebsd.org> References: <326ACF31.7FE3@OntheNet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01b1 (X11; I; FreeBSD 2.2-CURRENT i386) Tony Griffiths wrote: > > I'm having a problem with our WWW cacheing proxy (squid 1.0.???) falling > over when it gets to about 128 MB virtual. The error it gets is a > malloc() failure, so I presume that an attempt to expand VM has failed > because of some imposed limit! > > I checked the sources in .../vm/ and found references to > VM_MAXUSER_ADDRESS and some other defines, but could not see what > "config" parameters I should change to increase the maximum virtual > memory of a process. Also, I'm not sure if this is the problem because > it tweaked that I have 3 swap partitions, one of 128 MB and the other 2 > set at 120 MB (why 120... don't ask!). I was thinking that perhaps the > maximum virtual memory of a single process is limited by the largest > swap partition. > > Anyone knowledgeable in this area care to comment? > Yep, I am :-). Try adding the following kernel build options: option "MAXDSIZ=512UL*1024*1024" option "DFLDSIZ=256UL*1024*1024" This will set the default maximum dataspace size to 256MB, and the maximum to 512MB. It should work with no problems. The system dynamically adapts the rest of the params as needed. I haven't tested it, but give'er a try!!! John