[haiku-commits] Re: BRANCH midar-github.master - src/preferences/bluetooth src/servers/app src/kits/tracker src/add-ons/screen_savers/message headers/os/support

  • From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 20 Nov 2012 23:45:16 +0100

On 11/20/2012 04:06 PM, Jonathan Schleifer wrote:
Am 20.11.2012 um 14:03 schrieb Ingo Weinhold:
In Haiku we over-commit memory only for stack areas -- i.e., as you write, the 
area is created without
actually reserving physical memory. For other areas, including heap areas, 
memory is committed upfront, though.
Oh, interesting. I guess Haiku is almost the only operating system that still 
does it this way today.

At least Solaris does it exactly the same way. AIX can be configured to not overcommit (used to be the default a few years back IIRC). It looks like Windows does not generally overcommit memory as well if I understand [1] correctly.


[1] http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx

Other related posts: