6 messages in org.freebsd.freebsd-bugsRe: kern/4070: cannot access over 64M...| From | Sent On | Attachments |
|---|---|---|
| Jin Guojun[ITG] | Jul 9, 1997 11:35 am | |
| David Greenman | Jul 9, 1997 2:59 pm | |
| Jin Guojun[ITG] | Jul 9, 1997 3:39 pm | |
| Poul-Henning Kamp | Jul 9, 1997 11:16 pm | |
| David Greenman | Jul 10, 1997 2:45 am | |
| Poul-Henning Kamp | Jul 10, 1997 3:28 am |
| Subject: | Re: kern/4070: cannot access over 64MB memory | |
|---|---|---|
| From: | David Greenman (dg...@root.com) | |
| Date: | Jul 9, 1997 2:59:40 pm | |
| List: | org.freebsd.freebsd-bugs | |
The following reply was made to PR kern/4070; it has been noted by GNATS.
From: David Greenman <dg...@root.com> To: ji...@adv-pc-1.lbl.gov Cc: Free...@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