[SERVER-12567] Allow remapprivateview to relocate mappings for files on Windows Created: 31/Jan/14 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, MMAPv1, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
If this were allowed, we wouldn't need to use a bump allocator for choosing base addresses when memory mapping files. That bump allocation is a cheap trick to try to avoid having another allocation steal your addresses while remapping a file on Windows. However, on Windows, we have to block all readers and writers during remapping anyways, so it should be OK to change the base addresses for files. |