From owner-freebsd-questions@FreeBSD.ORG Thu Aug 7 16:42:38 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 840B1106567A for ; Thu, 7 Aug 2008 16:42:38 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.freebsd.org (Postfix) with ESMTP id 35E278FC2B for ; Thu, 7 Aug 2008 16:42:32 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.14.2/8.14.2) with ESMTP id m77GQ6Ah033518; Thu, 7 Aug 2008 11:26:07 -0500 (CDT) (envelope-from tinguely@casselton.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=casselton.net; s=ccnMail; t=1218126367; bh=3dlzZARJrfzdiaAvqcEro5Hg+zZd1brq2Tjg/pY 2fO0=; h=Date:From:Message-Id:To:Subject:Cc:In-Reply-To; b=aeGHRIaR C2+KdmvGnGPjRLEUQIwTUDCxYgNddy6hQvVnQmrxcQy8b/wkNpn7ixBoV1PnIg0kPcT WLwfchphLzcHpWs4oVkBm4+BfMKMKhr0VdtsgYtZGbwI5QsuPu6wZNm+CK0pw4uc/jX bkFByEb7f1gyndpMXeBSn8WzuuEjg= Received: (from tinguely@localhost) by casselton.net (8.14.2/8.14.2/Submit) id m77GQ6vf033517; Thu, 7 Aug 2008 11:26:06 -0500 (CDT) (envelope-from tinguely) Date: Thu, 7 Aug 2008 11:26:06 -0500 (CDT) From: Mark Tinguely Message-Id: <200808071626.m77GQ6vf033517@casselton.net> To: mkhitrov@gmail.com In-Reply-To: <489B1311.9020100@FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: Re: 64-bit Linux Binary Compatibility (for Matlab) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2008 16:42:38 -0000 > Date: Thu, 7 Aug 2008 09:47:45 -0400 > From: mkhitrov@gmail.com > To: freebsd-questions@freebsd.org > Apparently Matlab tries to allocate a continuous chunk of memory, and > we needed to upgrade to 64-bit hardware to give it access to more than > 1GB of memory, which is about the most that it was able to get before. > It's a lousy explanation, but I wasn't employed at this place when > this diagnosis was made. Large contiguous allocations have to occur during or soon after booting because of memory fragmentation. I can see that larger memory configurations on a 64 bit OS has a better chance of allocating big chunks like this. Make sure you have much more than 4G RAM since some hardware needs memory below 4GB, and the contiguous allocation at boot favors memory towards the top of the 4GB range. --Mark Tinguely.