Remove a lingering inaccuracy from mlock.2.

User wirings of the same address range don't stack.

Noted by:	Dan Nelson
MFC after:	3 days
This commit is contained in:
Mark Johnston 2018-03-20 20:45:47 +00:00
parent 3224bb3f77
commit f0eaf8ec5e

View File

@ -28,7 +28,7 @@
.\" @(#)mlock.2 8.2 (Berkeley) 12/11/93 .\" @(#)mlock.2 8.2 (Berkeley) 12/11/93
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd Jan 22, 2018 .Dd March 20, 2018
.Dt MLOCK 2 .Dt MLOCK 2
.Os .Os
.Sh NAME .Sh NAME
@ -78,9 +78,7 @@ are removed.
Multiple processes may have the same physical pages locked via their own Multiple processes may have the same physical pages locked via their own
virtual address mappings. virtual address mappings.
A single process may likewise have pages multiply-locked via different virtual A single process may likewise have pages multiply-locked via different virtual
mappings of the same pages or via nested mappings of the same physical pages.
.Fn mlock
calls on the same address range.
Unlocking is performed explicitly by Unlocking is performed explicitly by
.Fn munlock .Fn munlock
or implicitly by a call to or implicitly by a call to