Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!mcsun!Germany.EU.net!cat-ufg.de!wis
From: wis@olly.cat-ufg.de (Bernd Wiserner)
Subject: Re: Virtual memory problem
Message-ID: <C94o7L.D49@cat-ufg.de>
Sender: wis@olly (Bernd Wiserner)
Nntp-Posting-Host: olly
Organization: CAT Computer Anwendungs-Technologie GmbH
References: <1993Jun24.015842.21623@news.arc.nasa.gov>
Date: Thu, 24 Jun 1993 13:30:57 GMT
Lines: 38
In article <1993Jun24.015842.21623@news.arc.nasa.gov>, root@wanderer.nsi.nasa.gov (Michael C. Newell) writes:
!> Stuff deleted ...
|> So I wrote a simple C program that went into an infinte
|> loop doing mallocs for 1K blocks of memory. It was able
|> to get 3072 [interesting number...] before it ran out
|> of VM. The drive with the 88Mb swap partition rattled
> In rooting around the malloc related code I came across
|> the constant "DFLDSIZ" in "/sys/i386/include/vmparam.h".
|> It is supposed to be the "initial data size limit", and
|> was set to "6*1024*1024", or 6Mb. I changed this to
|> "16*1024*1024" and rebuilt the kernel. The little C
|> program now was able to allocate 8192 1K blocks. This
|> was enough to get past the "insufficient virtual memory"
|> errors [unfortunately others followed... :{(]
|>
|> So my question is, "Why is this happening?" Why can't
|> I allocate some reasonably close-to-16Mb amount of
|> virtual memory? Is "DFLDSIZ" really the MAXIMUM amount
|> (there is another constant "MAXDSIZ" set to 32Mb which
|> would seem to perform that function.)
|>
|> ??
|>
|> Thanks,
|>
|> Mike Newell
|> NASA Advanced Network Applications Group
Try this : limit datasize xxx ( where xxx is the desired size )
Note that this works only in c-shell ( or tcshell ).
If you do this you don't need to recompile the kernel.
However you can't increase the size over 32Meg.
mfg B.Wiserner
wis@cat-ufg.de