From owner-freebsd-bugs  Wed Jul  9 15:00:02 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA14718
          for bugs-outgoing; Wed, 9 Jul 1997 15:00:02 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA14688;
          Wed, 9 Jul 1997 15:00:01 -0700 (PDT)
Date: Wed, 9 Jul 1997 15:00:01 -0700 (PDT)
Message-Id: <199707092200.PAA14688@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: David Greenman <dg@root.com>
Subject: Re: kern/4070: cannot access over 64MB memory 
Reply-To: David Greenman <dg@root.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4070; it has been noted by GNATS.

From: David Greenman <dg@root.com>
To: jin@adv-pc-1.lbl.gov
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/4070: cannot access over 64MB memory 
Date: Wed, 09 Jul 1997 14:59:15 -0700

 >	options	"MAXMEM=(256x1024)"
 >	supposes to enable more than 64 MB memory, but only 64MB memory
 >	can be accessed regardless how many memory detected by kernel.
 >
 ># dmesg | grep mem
 >real memory  = 134217728 (131072K bytes)
 >Physical memory hole(s):
 >avail memory = 127311872 (124328K bytes)
 ...
 >mem-test [S20-1] : no enough core available for inbuf -> 1H x 6000000H = 100663296; Error<12> Cannot allocate memory
 
    The error is returned because you hit the process resource limit, not
 because the system didn't have enough memory.
 
 ># limit
 ...
 >datasize        131072 kbytes
 
    Malloc is kind of strange when it comes to allocating the virtual address
 space and will consume up to twice the amount requested. If you want to malloc
 more than 64MB, you'll need to further increase the data limit.
 
 -DG
 
 David Greenman
 Core-team/Principal Architect, The FreeBSD Project