From owner-freebsd-hackers Fri Jun 19 10:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24435 for freebsd-hackers-outgoing; Fri, 19 Jun 1998 10:20:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24315 for ; Fri, 19 Jun 1998 10:19:51 -0700 (PDT) (envelope-from syang@DIRHIT.COM) Received: from moe.dirhit.com (d-hit.dirhit.com [146.115.235.211]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id NAA24841 for ; Fri, 19 Jun 1998 13:19:31 -0400 (EDT) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Fri, 19 Jun 1998 12:54:24 -0400 Message-ID: <839A86AB6CE4D111A52200104B938D435B40@MOE> From: Steven Yang To: "'freebsd-hackers@FreeBSD.org'" Subject: memory question Date: Fri, 19 Jun 1998 12:54:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am working with gdbm, and would like to create very large files (hopefully more than 1GB). Unfortunately, I have run into a problem where no process seems to be able to use more than 16MB of RAM. gdbm gives me the following error message: gdbm fatal: malloc error I then decided to write a program that did a malloc of 16MB and 17MB, and the malloc of 16MB succeeded, but the malloc of 17MB failed. I also wrote a program that did a malloc of 16MB and 1MB at the same time, which also failed. It appears that there is a default limitation of 16MB of RAM per process, and although we tried setting MAXMEM in the configuration file (taken from a LINT option) to 128MB (the RAM in our system), the tests still failed (yes, we recompiled the kernel). How do I get around this limitation? Furthermore, must gdbm load the whole database into memory in order to insert a record? - Steven Yang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message