Documentaiton claims 2GB limit on memory mapped IO

Question

This document at

https://learn.microsoft.com/en-us/windows/win32/memory/creating-a-file-mapping-object

creating-a-file-mapping-object

Says

The size of a file mapping object that is backed by a named file is limited by disk space. The size of a file view is limited to the largest available contiguous block of unreserved virtual memory. This is at most 2 GB minus the virtual memory already reserved by the process.

Surly this is vestigial. It suggests the document is quite old.

Is there some new way of doing Memory Mapped IO that I should be using?

Answer 1

There is no some new way of doing Memory Mapped IO. But CreateFileMapping and MapViewOfFile both support those bigger than 2GB operation.