mirror of https://github.com/mkerrisk/man-pages
mmap.2: MAP_FIXED is no longer discouraged
MAP_FIXED has been widely used for a very long time, yet the man page still claims that "the use of this option is discouraged". The documentation assumes that "less portable" == "must be discouraged". Instead of discouraging something that is so useful and widely used, change the documentation to explain its limitations better. Signed-off-by: John Hubbard <jhubbard@nvidia.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
0f24751222
commit
ffa518803e
|
@ -222,8 +222,10 @@ part of the existing mapping(s) will be discarded.
|
|||
If the specified address cannot be used,
|
||||
.BR mmap ()
|
||||
will fail.
|
||||
Because requiring a fixed address for a mapping is less portable,
|
||||
the use of this option is discouraged.
|
||||
Software that aspires to be portable should use this option with care, keeping
|
||||
in mind that the exact layout of a process' memory map is allowed to change
|
||||
significantly between kernel versions, C library versions, and operating system
|
||||
releases.
|
||||
.TP
|
||||
.B MAP_GROWSDOWN
|
||||
This flag is used for stacks.
|
||||
|
|
Loading…
Reference in New Issue