[haiku] Re: Fwd: x86_64 build failed with gcc4 based x86_64 linux distros
- From: Andrew Hudson <hudsonco1@xxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Wed, 27 Jul 2011 09:46:59 -0400 (EDT)
OK, thanks for the info. Yes, I agree that 4 GB is good enough for basic
purposes. However, the definition of a successful product is when people use it
for unintended purposes :-) - Andrew
But really, the intended target for Haiku doesn't really need that much
yet.
-----Original Message-----
From: François Revol <revol@xxxxxxx>
To: haiku <haiku@xxxxxxxxxxxxx>
Sent: Wed, Jul 27, 2011 5:19 am
Subject: [haiku] Re: Fwd: x86_64 build failed with gcc4 based x86_64 linux
distros
Le mercredi 27 juillet 2011 à 08:59 -0400, Andrew Hudson a écrit :
> I am curious to know a few things about Haiku memory limitations under
> 32-bit.
For instance:
> What is the largest single amount from malloc (or equivalent)?
> What is largest amount of memory one process can address?
4GB, from which 2GB is the kernel space.
> What is the largest amount of memory Haiku can address?
Currently 4GB AFAIK.
The limitations that BeOS had and Haiku had also due to mapping the
whole physical RAM into kernel space was removed some years ago (Linux
also used to have this limitations years ago).
> Are there any 'special fixups' or tricks or special cases for more memory?
Our kernel should now support PAE, so it should at least support up to
4GB or RAM, not sure about more.
But really, the intended target for Haiku doesn't really need that much
yet.
François.
Other related posts:
