Date: Thu, 7 Aug 2008 11:03:40 -0400 From: "Maxim Khitrov" <mkhitrov@gmail.com> To: "Sean Cavanaugh" <millenia2000@hotmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: 64-bit Linux Binary Compatibility (for Matlab) Message-ID: <26ddd1750808070803v762e536dofd72d8b3f17c5baa@mail.gmail.com> In-Reply-To: <BAY126-W112780E26097569F34F757CA750@phx.gbl> References: <26ddd1750808070647yf0a9205u514c6ba87fbf97a5@mail.gmail.com> <BAY126-W112780E26097569F34F757CA750@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 7, 2008 at 10:52 AM, Sean Cavanaugh <millenia2000@hotmail.com> wrote: > > >> Date: Thu, 7 Aug 2008 09:47:45 -0400 >> From: mkhitrov@gmail.com >> To: freebsd-questions@freebsd.org >> Subject: 64-bit Linux Binary Compatibility (for Matlab) > >> 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. >> > > running 32-bit gives you access to 4GB of RAM, not 1. there is some address > space that is used up by hardware such as video cards that will reduce that > number reported by the OS. > I know that, the key word there is continuous space. In either case, I'm only repeating what was said to me as the reason for purchasing a brand new server - run in 64-bit mode to give Matlab more virtual memory. It may end up being the case that the problem was completely unrelated. I'll know in about an hour :) - Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26ddd1750808070803v762e536dofd72d8b3f17c5baa>