From owner-freebsd-hackers Sun Aug 2 20:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16264 for freebsd-hackers-outgoing; Sun, 2 Aug 1998 20:00:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net ([209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA16258 for ; Sun, 2 Aug 1998 20:00:53 -0700 (PDT) (envelope-from david@sparks.net) From: david@sparks.net Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0z3ArW-0006N0-00; Sun, 2 Aug 1998 23:00:38 -0400 Date: Sun, 2 Aug 1998 23:00:38 -0400 (EDT) Reply-To: david@sparks.net To: freebsd-hackers@FreeBSD.ORG Subject: malloc question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From lurking on this list a long time, I think I understand that the 4.4bsd malloc will always attempt to grab the next higher power of two of memory. That would certainly fit with my observed behavior. I've an application which contains very little code (text), but a huge data area. Specifically, I want to be able to allocate 128 MB to an array and have a meg or two for code on my 160 MB system. But I get "can't allocate memory" errors on my 2.2.6R system. My login_class is root, and bash reports "unlimited" for shell datasize limits. vm.maxdsize, a possible problem on a bsdi system, doesn't seem to exist on FreeBSD. What am I missing? I must be able to run a 130 MB program on a 160 MB system:) Thanks, --- David ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message