Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!spool.mu.edu!news.cs.indiana.edu!mips!cs.uoregon.edu!ns.uoregon.edu!milton!uw-beaver!fluke!ssc-vax!ian
From: ian@ssc-vax.UUCP (Ian R. Searle)
Newsgroups: comp.unix.ultrix
Subject: Re: Malloc Problems with DECstation 5000/200
Summary: Problem Solved, sort-of
Keywords: Malloc, RISC, Ultrix 4.1
Message-ID: <3858@ssc-bee.ssc-vax.UUCP>
Date: 16 Apr 91 17:38:11 GMT
References: <3853@ssc-bee.ssc-vax.UUCP>
Distribution: usa
Organization: Boeing Aerospace & Electronics, Seattle WA
Lines: 16


Hello, as it turns out I have "sort-of" solved my own problem, but
I would still like to hear from anyone who can explain the remaining
puzzle.

The problem of a single process size not growing beyond 60-70
Mbytes when we have 157 Mbytes of swap was due to the parameters
in /usr/sys/conf/mips/NODE-NAME (configuration file). Specifically
maxdsiz was set to 64. Upping this to 128 and rebuilding the kernel
solved our problems, sort-of.

We still cannot malloc a single chunk of memory larger than 32
Mbytes when using the standard malloc. When we link with -lmalloc
we can get up to 128 Mbytes (the value of maxdsiz). Why the diff??

thanks in advance, Ian Searle.