From owner-freebsd-current Tue Aug 29 21:20:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id 46B8C37B424 for ; Tue, 29 Aug 2000 21:20:52 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 29 Aug 2000 23:18:45 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e7U4FsV00427 for ; Tue, 29 Aug 2000 23:15:54 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e7U4FsV05641 for ; Tue, 29 Aug 2000 23:15:54 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200008300415.e7U4FsV05641@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Heap colliding with mmaped areas? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Aug 2000 23:15:54 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a situation where some device files are being mmaped (to the tune of a couple of hundred megs) and then there's some memory allocation happening. The memory allocation ends up failing, even though the amount it appears to be requesting would make the process a long way off its maximum allowed size. Is there a way of adjusting where the heap starts in the address space? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message