On Sat, Jun 08, 2002 at 10:40:54AM -0700, Matthew Dillon wrote: > <options MAXDSIZ="(1024*1024*1024)" > <options MAXSSIZ="(256*1024*1024)" > > But it doesn't make much sense. A 64 megabyte stack ought > to be plenty, as should the default 512MB data size. > > It should be noted that mmap() uses whatever VM space > remains after MAXDSIZ and MAXSSIZ have been reserved, so > increasing MAXDSIZ reduces the amount of VM available > to mmap(). Still, a 1 GB MAXDSIZ should not result in > system utilities / servers running out of mmap() space! > Userland has 3G of VM space to play with.
I'm running into some similar issues when trying to make Squid eat as much as possible of the 4 GB memory I have installed in a Compaq ProLiant DL 380 G2. At first, Squid seems to die and restart when trying to allocate memory above 512 MB. By tuning MAXDSIZ, I have made it use up to around 2 GB. If I set MAXDSIZ (I now do it in loader.conf with kern.maxdsiz) above around 2950 MB, init starts failing upon boot: init in malloc(): error mmap(2) failed, check limits init in malloc(): warning: recursive call Does anyone have any clues on how to overcome this? I'll be trying out the the dlmalloc library that is distributed with Squid, but I suppose I do need a 4 GB maximum data size to be able to make Squid actually use 4 GB. Is this possible, or am I being totally foolish? Any hint very appreciated. :-) Cheers, -- Anders. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
