Memory-mapped I/O (the GNU c Library) > 자유게시판

• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

On modern operating techniques, it is feasible to mmap (pronounced "em-map") a file to a area of memory. When this is done, the file will be accessed just like an array in this system. This is extra environment friendly than read or write, as only the regions of the file that a program truly accesses are loaded. Accesses to not-but-loaded elements of the mmapped region are dealt with in the identical approach as swapped out pages. Since mmapped pages could be saved back to their file when physical memory is low, it is feasible to mmap recordsdata orders of magnitude larger than both the bodily memory and swap house. The only limit is address house. The theoretical limit is 4GB on a 32-bit machine - nevertheless, the precise limit will likely be smaller since some areas might be reserved for different functions. If the LFS interface is used the file dimension on 32-bit systems isn't restricted to 2GB (offsets are signed which reduces the addressable space of 4GB by half); the full 64-bit are available.

Memory mapping only works on whole pages of memory. Thus, addresses for mapping must be page-aligned, and length values can be rounded up. Preliminary: | MT-Protected | AS-Secure | AC-Secure | See POSIX Security Concepts. 1) in the file open on filedes. A brand new reference for the file specified by filedes is created, which is not removed by closing the file. NULL expresses no preference. Any earlier mapping at that deal with is mechanically removed. NONE reserves a area of deal with house for future use. The mprotect function can be utilized to alter the safety flags. Non-public have to be specified. This specifies that writes to the area ought to never be written again to the hooked up file. As a substitute, a duplicate is made for the process, and the region shall be swapped normally if memory runs low. No different process will see the modifications. This specifies that writes to the area can be written again to the file.

Changes made will probably be shared immediately with other processes mmaping the identical file. Be aware that precise writing might take place at any time. You need to make use of msync, described beneath, if it will be significant that other processes using typical I/O get a consistent view of the file. This forces the system to make use of the exact mapping deal with specified in tackle and fail if it can’t. This flag tells the system to create an nameless mapping, not connected to a file. Anonymous maps are used as the fundamental primitive to increase the heap on some programs. They are also helpful to share information between a number of tasks with out creating a file. On some systems utilizing non-public nameless mmaps is extra environment friendly than utilizing malloc for large blocks. This isn't an issue with the GNU C Library, Memory Wave Program as the included malloc routinely uses mmap the place applicable. This requests that the system makes use of another page dimension which is bigger than the default web page measurement for the mapping.

For some workloads, rising the page measurement for large mappings improves performance because the system needs to handle far fewer pages. For different workloads which require frequent switch of pages between storage or completely different nodes, the decreased web page granularity may trigger performance problems as a result of increased page measurement and bigger transfers. As a way to create the mapping, the system wants physically contiguous memory of the scale of the elevated page size. HUGETLB mappings are affected by memory fragmentation, and their creation can fail even if loads of Memory Wave Program is accessible within the system. Not all file programs assist mappings with an increased web page measurement. HUGETLB flag is particular to Linux. FAILED for an error. Both tackle was unusable (as a result of it isn't a multiple of the applicable web page size), or inconsistent flags have been given. HUGETLB was specified, the file or system does not help giant web page sizes. Either there will not be enough memory for the operation, or the process is out of deal with space.

This file is of a sort that doesn’t help mapping. The file is on a filesystem that doesn’t help mapping. Preliminary: | MT-Protected | AS-Protected | AC-Safe | See POSIX Security Concepts. On 32-bit systems this allows the file associated with the filedes descriptor to be bigger than 2GB. filedes have to be a descriptor returned from a name to open64 or fopen64 and freopen64 the place the descriptor is retrieved with fileno. 64 this operate is definitely available beneath the identify mmap. I.e., the brand new, prolonged API using sixty four bit file sizes and offsets transparently replaces the outdated API. Preliminary: | MT-Protected | AS-Safe | AC-Safe | See POSIX Safety Concepts. It is safe to unmap multiple mappings in one command, or include unmapped house within the range. Additionally it is possible to unmap only a part of an existing mapping. However, only complete pages could be removed. If size shouldn't be an excellent variety of pages, it will likely be rounded up.