From: Michael Kerrisk Date: Tue, 30 Aug 2016 19:18:09 +0000 (+1200) Subject: mlock.2: Minor tweaks to Sebastian Andrzej Siewior's patch X-Git-Tag: man-pages-4.08~191 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=cbac502be227c668b55a87ba3e193721ede2ae67;p=thirdparty%2Fman-pages.git mlock.2: Minor tweaks to Sebastian Andrzej Siewior's patch Signed-off-by: Michael Kerrisk --- 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