mlock.2: Minor tweaks to Sebastian Andrzej Siewior's patch

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-08-31 07:18:09 +12:00
parent fb08a0954e
commit cbac502be2
1 changed files with 7 additions and 7 deletions

View File

@ -352,17 +352,17 @@ and are cleared during an
Note that
.BR fork (2)
will prepare the address space for a copy-on-write operation. The consequence
is that any write access that follows will cause a page fault which in turn may
cause high latencies for a real-time process. Therefore it is crucial not to
invoke
will prepare the address space for a copy-on-write operation.
The consequence is that any write access that follows will cause
a page fault that in turn may cause high latencies for a real-time process.
Therefore, it is crucial not to invoke
.BR fork (2)
after the
after an
.BR mlockall ()
or
.BR mlock ()
operation not even from thread which runs at a low priority within a process
which also has a thread running at elevated priority.
operation\(emnot even from a thread which runs at a low priority within
a process which also has a thread running at elevated priority.
The memory lock on an address range is automatically removed
if the address range is unmapped via