mremap.2: Move a paragraph from DESCRIPTION to NOTES

The paragraph on Linux VM is rather generic, and does not belong
in DESCRIPTION. In fact, I'm not sure it even belongs in this
page.  At the least, let's move it to NOTES.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2020-04-16 08:16:01 +02:00
parent 8c97c565ee
commit f15e32e3b9
1 changed files with 14 additions and 14 deletions

View File

@ -74,20 +74,6 @@ If a new mapping is requested via this method, then the
.B MREMAP_MAYMOVE
flag must also be specified.
.PP
In Linux, memory is divided into pages.
A process has (one or)
several linear virtual memory segments.
Each virtual memory segment has one
or more mappings to real memory pages (in the page table).
Each virtual memory segment has its own
protection (access rights), which may cause
a segmentation violation
.RB ( SIGSEGV )
if the memory is accessed incorrectly (e.g.,
writing to a read-only segment).
Accessing virtual memory outside of the
segments will also cause a segmentation violation.
.PP
The \fIflags\fP bit-mask argument may be 0, or include the following flag:
.TP
.B MREMAP_MAYMOVE
@ -279,6 +265,20 @@ mapping between virtual addresses and memory pages.
This can be used to implement a very efficient
.BR realloc (3).
.PP
In Linux, memory is divided into pages.
A process has (one or)
several linear virtual memory segments.
Each virtual memory segment has one
or more mappings to real memory pages (in the page table).
Each virtual memory segment has its own
protection (access rights), which may cause
a segmentation violation
.RB ( SIGSEGV )
if the memory is accessed incorrectly (e.g.,
writing to a read-only segment).
Accessing virtual memory outside of the
segments will also cause a segmentation violation.
.PP
If
.BR mremap ()
is used to move or expand an area locked with