Memory-Mapped File: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "---- __NOTOC__" to "---- __NOTOC__") |
m (Text replacement - ". ----" to ". ----") |
||
| Line 1: | Line 1: | ||
A [[Memory-Mapped File]] is a segment of [[virtual memory]] which has been assigned a direct byte-for-byte correlation with some portion of a [[data file]] or [[data file-like resource]]. | A [[Memory-Mapped File]] is a segment of [[virtual memory]] which has been assigned a direct byte-for-byte correlation with some portion of a [[data file]] or [[data file-like resource]]. | ||
* <B>See:</B> [[Virtual Memory]], [[Operating System]], [[File Descriptor]], [[Primary Memory]]. | * <B>See:</B> [[Virtual Memory]], [[Operating System]], [[File Descriptor]], [[Primary Memory]]. | ||
---- | ---- | ||
---- | ---- | ||
Latest revision as of 17:23, 21 September 2021
A Memory-Mapped File is a segment of virtual memory which has been assigned a direct byte-for-byte correlation with some portion of a data file or data file-like resource.
References
2014
- (Wikipedia, 2014) ⇒ http://en.wikipedia.org/wiki/memory-mapped_file Retrieved:2014-8-3.
- A memory-mapped file is a segment of virtual memory which has been assigned a direct byte-for-byte correlation with some portion of a file or file-like resource. This resource is typically a file that is physically present on-disk, but can also be a device, shared memory object, or other resource that the operating system can reference through a file descriptor. Once present, this correlation between the file and the memory space permits applications to treat the mapped portion as if it were primary memory.