Section: Linux Programmer's Manual (2)
Return to Main Contents
remap_file_pages - create a nonlinear file mapping
#define _GNU_SOURCE /* See feature_test_macros(7) */
int remap_file_pages(void *addr, size_t size, int prot,
size_t pgoff, int flags);
this system call is (since Linux 3.16) deprecated and will
eventually be replaced by a slower in-kernel emulation.
Those few applications that use this system call should
consider migrating to alternatives.
system call is used to create a nonlinear mapping, that is, a mapping
in which the pages of the file are mapped into a nonsequential order
The advantage of using
over using repeated calls to
is that the former approach does not require the kernel to create
additional VMA (Virtual Memory Area) data structures.
To create a nonlinear mapping we perform the following steps:
to create a mapping (which is initially linear).
This mapping must be created with the
Use one or more calls to
to rearrange the correspondence between the pages of the mapping
and the pages of the file.
It is possible to map the same page of a file
into multiple locations within the mapped region.
arguments specify the region of the file that is to be relocated
within the mapping:
is a file offset in units of the system page size;
is the length of the region in bytes.
argument serves two purposes.
First, it identifies the mapping whose pages we want to rearrange.
must be an address that falls within
a region previously mapped by a call to
specifies the address at which the file pages
will be placed.
The values specified in
should be multiples of the system page size.
If they are not, then the kernel rounds
to the nearest multiple of the page size.
argument must be specified as 0.
argument has the same meaning as for
but all flags other than
On error, -1 is returned, and
is set appropriately.
does not refer to a valid mapping
created with the
system call appeared in Linux 2.5.46;
glibc support was added in version 2.3.3.
system call is Linux-specific.
Since Linux 2.6.23,
creates non-linear mappings only
on in-memory file systems such as tmpfs, hugetlbfs or ramfs.
On filesystems with a backing store,
is not much more efficient than using
to adjust which parts of the file are mapped to which addresses.
This page is part of release 3.74 of the Linux
A description of the project,
information about reporting bugs,
and the latest version of this page,
can be found at
- RETURN VALUE
- CONFORMING TO
- SEE ALSO