| manpages.info - online man pages | ![]() |
|||
|
mmap (2) Table of Contents
Namemmap - map files or devices into memory
Synopsis
#include <sys/types.h>
void *
DescriptionThe mmap function causes the pages starting at addr and continuing for at most len bytes to be mapped from the object described by fd, starting at byte offset offset. If offset or len is not a multiple of the pagesize, the mapped region may extend past the specified range.
If addr is non-zero, it is used as a hint to the system. (As a convenience to the system, the actual address of the region may differ from the address supplied.) If addr is zero, an address will be selected by the system. The actual starting address of the region is returned. A successful mmap deletes any previous mapping in the allocated address range.
The protections (region accessibility) are specified in the prot argument by or'ing the following values:
PROT_WRITE Pages may be written.
The flags parameter specifies the type of the mapped object, mapping options and whether modifications made to the mapped copy of the page are private to the process or are to be shared with other references. Sharing, mapping type and options are specified in the flags argument by or'ing the following values:
MAP_SHARED Modifications are shared.
The close(2) function does not unmap pages, see munmap(2) for further information.
The current design does not allow a process to specify the location of swap space. In the future we may define an additional mapping type, MAP_SWAP, in which the file descriptor argument specifies a file or device to which swapping should be done.
Return ValuesUpon successful completion, mmap returns a pointer to the mapped region. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ErrorsMmap() will fail if:
See Alsogetpagesize(2) , msync(2) , munmap(2) , mprotect(2) , madvise(2) , mincore(2) , mlock(2)
|