mmap.2: Note that MAP_STACK exists on some other systems

As noted in man-pages commit 99c3a00027,
MAP_STACK exists on at least OpenBSD and FreeBSD.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2019-11-14 12:52:40 +01:00
parent 1b54731692
commit d3d881232b
1 changed files with 4 additions and 0 deletions

View File

@ -403,6 +403,7 @@ is supported for private mappings only since Linux 2.6.23.
.BR MAP_STACK " (since Linux 2.6.27)" .BR MAP_STACK " (since Linux 2.6.27)"
Allocate the mapping at an address suitable for a process Allocate the mapping at an address suitable for a process
or thread stack. or thread stack.
.IP
This flag is currently a no-op, This flag is currently a no-op,
but is used in the glibc threading implementation so that but is used in the glibc threading implementation so that
if some architectures require special treatment for stack allocations, if some architectures require special treatment for stack allocations,
@ -412,6 +413,9 @@ support can later be transparently implemented for glibc.
.\" http://thread.gmane.org/gmane.linux.kernel/720412 .\" http://thread.gmane.org/gmane.linux.kernel/720412
.\" "pthread_create() slow for many threads; also time to revisit 64b .\" "pthread_create() slow for many threads; also time to revisit 64b
.\" context switch optimization?" .\" context switch optimization?"
A further reason to employ this flag is portability:
.BR MAP_SHARED
exists (and has an effect) on some other systems (e.g., some of the BSDs).
.TP .TP
.BR MAP_SYNC " (since Linux 4.15)" .BR MAP_SYNC " (since Linux 4.15)"
This flag is available only with the This flag is available only with the