diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-08-31 07:18:09 +1200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-08-31 07:23:08 +1200 |
| commit | cbac502be227c668b55a87ba3e193721ede2ae67 (patch) | |
| tree | 4ac0625bb1140c9b849d80123f533c3ec254b955 /man2 | |
| parent | fb08a0954ecfde61ad671ce60ed22c358298fe28 (diff) | |
| download | man-pages-cbac502be227c668b55a87ba3e193721ede2ae67.tar.gz | |
mlock.2: Minor tweaks to Sebastian Andrzej Siewior's patch
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man2')
| -rw-r--r-- | man2/mlock.2 | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/man2/mlock.2 b/man2/mlock.2 index 27f80f6664..08387b0bbe 100644 --- a/man2/mlock.2 +++ b/man2/mlock.2 @@ -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 |