Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!brl-adm!seismo!mimsy!chris
From: chris@mimsy.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Not enough core: how to cure?
Message-ID: <5433@mimsy.UUCP>
Date: Fri, 13-Feb-87 22:58:38 EST
Article-I.D.: mimsy.5433
Posted: Fri Feb 13 22:58:38 1987
Date-Received: Sun, 15-Feb-87 00:57:12 EST
References: <1010@ur-valhalla.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 28
Keywords: BSD4.2, VAX 11/750, core

In article <1010@ur-valhalla.UUCP> badri@ur-valhalla.UUCP (Badri Lokanathan)
writes:
>Wire1 (Works)
>text	data	bss	dec	hex
>384000	66560	6071296	6521856	638400
>Wire2 (Does not work)
>text	data	bss	dec	hex
>384000	66560	6988076	7438636	71812c

>ctod(ds) = 12906 exceeds maxdmap = 12256 in /sys/machine/vm_machdep.c

maxdmap can be computed as a function of DMMIN, DMMAX, and NDMAP.
`dmap's are swap allocation chunks.  Swap space is allocated in
contiguous chunks of varying sizes, increasing by powers of two
from DMMIN to DMMAX, then repeating at DMMAX.  Your DMMIN is 32,
your DMMAX is 1024, and your NDMAP is 16:

	maxdmap = 32+64+128+256+512+11*1024 = 12256

which is 12256*512 = 6275072 bytes of data space.

The way to alter this limit is to change any of those parameters.
Making DMMIN 64 will cause more fragmentation, but will give you
a maxdmap of 13248; making DMMAX 2048 instead will change it to
22496, or 11517952 bytes.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
UUCP:	seismo!mimsy!chris	ARPA/CSNet:	chris@mimsy.umd.edu