LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

get_mempolicy.2, mbind.2, mlock.2, set_mempolicy.2, bootparam.7, packet.7: grfix: s/memory mapped/memory-mapped/ when used attributively 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-01-05 11:00:31 +13:00
parent 084cf3d1cd
commit 9a141bfb1f
6 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man2/get_mempolicy.2
View File

@ -155,7 +155,7 @@ argument,
the node ID of the next node that will be used for
interleaving of internal kernel pages allocated on behalf of the process.
.\" Note: code returns next interleave node via 'mode' argument -Lee Schermerhorn
These allocations include pages for memory mapped files in
These allocations include pages for memory-mapped files in
process memory ranges mapped using the
.BR mmap (2)
call with the

4
man2/mbind.2
View File

@ -73,7 +73,7 @@ a region of memory created using the
.BR mmap (2)
system call with the
.BR MAP_ANONYMOUS \(emor
a memory mapped file, mapped using the
a memory-mapped file, mapped using the
.BR mmap (2)
system call with the
.B MAP_PRIVATE
@ -406,7 +406,7 @@ This system call is Linux-specific.
For information on library support, see
.BR numa (7).
NUMA policy is not supported on a memory mapped file range
NUMA policy is not supported on a memory-mapped file range
that was mapped with the
.B MAP_SHARED
flag.

2
man2/mlock.2
View File

@ -94,7 +94,7 @@ the process.
Lock all pages which will become mapped into the address space of the
process in the future.
These could be for instance new pages required
by a growing heap and stack as well as new memory mapped files or
by a growing heap and stack as well as new memory-mapped files or
shared memory regions.
.PP
If

4
man2/set_mempolicy.2
View File

@ -58,12 +58,12 @@ address space outside of memory ranges
controlled by a more specific policy set by
.BR mbind (2).
The process default policy also controls allocation of any pages for
memory mapped files mapped using the
memory-mapped files mapped using the
.BR mmap (2)
call with the
.B MAP_PRIVATE
flag and that are only read [loaded] from by the process
and of memory mapped files mapped using the
and of memory-mapped files mapped using the
.BR mmap (2)
call with the
.B MAP_SHARED

4
man7/bootparam.7
View File

@ -756,7 +756,7 @@ Syntax:
.IP
The
.I mem_base
value is the value of the memory mapped I/O region that
value is the value of the memory-mapped I/O region that
the card uses.
This will usually be one of the following values:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
@ -860,7 +860,7 @@ you will then have to use a boot argument of the form:
.IP
The
.I mem_base
value is the value of the memory mapped I/O region that
value is the value of the memory-mapped I/O region that
the card uses.
This will usually be one of the following values:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.

4
man7/packet.7
View File

@ -323,7 +323,7 @@ metadata structure and alignment padding.
This integer option reserves additional headroom.
.TP
.BR PACKET_RX_RING
Create a memory mapped ring buffer for asynchronous packet reception.
Create a memory-mapped ring buffer for asynchronous packet reception.
The packet socket reserves a contiguous region of application address
space, lays it out into an array of packet slots and copies packets
(up to
@ -390,7 +390,7 @@ in the Linux kernel source tree.
.TP
.BR PACKET_TX_RING " (since Linux 2.6.31)"
.\" commit 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1
Create a memory mapped ring buffer for packet transmission.
Create a memory-mapped ring buffer for packet transmission.
This option is similar to
.BR PACKET_RX_RING
and takes the same arguments.