Documentaiton claims 2GB limit on memory mapped IO

NumericalFunctional 21 Reputation points
2021-06-21T01:42:23.023+00:00

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?

Windows API - Win32
Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,772 questions
0 comments No comments
{count} votes

Accepted answer
  1. Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff
    2021-06-21T07:36:17.167+00:00

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

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.