The "too small to fail" memory-allocation rule
The "too small to fail" memory-allocation rule
Posted Dec 24, 2014 14:12 UTC (Wed) by patrakov (subscriber, #97174)In reply to: The "too small to fail" memory-allocation rule by ibukanov
Parent article: The "too small to fail" memory-allocation rule
This phrase is not 100% accurate:
"overcommit is not available (lack of fork in Windows API allows for that)"
It is not the lack of fork() that makes overcommit "unneeded", but an explicit decision. Windows MapViewOfFile() API allows creation of copy-on-write mappings (which are usually the basis for overcommit) through the FILE_MAP_COPY flag. Although, as documented, Windows does always reserve the whole size of the memory region in the pagefile.
See http://msdn.microsoft.com/en-us/library/windows/desktop/a...