2 .\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
3 .\" Copyright 1989 AT&T
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH MLOCK 3C "Apr 10, 2007"
9 mlock, munlock \- lock or unlock pages in memory
15 \fBint\fR \fBmlock\fR(\fBcaddr_t\fR \fIaddr\fR, \fBsize_t\fR \fIlen\fR);
20 \fBint\fR \fBmunlock\fR(\fBcaddr_t\fR \fIaddr\fR, \fBsize_t\fR \fIlen\fR);
23 .SS "Standard conforming"
28 \fBint\fR \fBmlock\fR(\fBconst void *\fR \fIaddr\fR, \fBsize_t\fR \fIlen\fR);
33 \fBint\fR \fBmunlock\fR(\fBconst void *\fR \fIaddr\fR, \fBsize_t\fR \fIlen\fR);
39 The \fBmlock()\fR function uses the mappings established for the address range
40 [\fIaddr, addr + len\fR) to identify pages to be locked in memory. If the page
41 identified by a mapping changes, such as occurs when a copy of a writable
42 \fBMAP_PRIVATE\fR page is made upon the first store, the lock will be
43 transferred to the newly copied private page.
46 The \fBmunlock()\fR function removes locks established with \fBmlock()\fR.
49 A given page may be locked multiple times by executing an \fBmlock()\fR through
50 different mappings. That is, if two different processes lock the same page,
51 then the page will remain locked until both processes remove their locks.
52 However, within a given mapping, page locks do not nest \(mi multiple
53 \fBmlock()\fR operations on the same address in the same process will all be
54 removed with a single \fBmunlock()\fR. Of course, a page locked in one process
55 and mapped in another (or visible through a different mapping in the locking
56 process) is still locked in memory. This fact can be used to create
57 applications that do nothing other than lock important data in memory, thereby
58 avoiding page I/O faults on references from other processes in the system.
61 The contents of the locked pages will not be transferred to or from disk except
62 when explicitly requested by one of the locking processes. This guarantee
63 applies only to the mapped data, and not to any associated data structures
64 (file descriptors and on-disk metadata, among others).
67 If the mapping through which an \fBmlock()\fR has been performed is removed, an
68 \fBmunlock()\fR is implicitly performed. An \fBmunlock()\fR is also performed
69 implicitly when a page is deleted through file removal or truncation.
72 Locks established with \fBmlock()\fR are not inherited by a child process after
73 a \fBfork()\fR and are not nested.
76 Attempts to \fBmlock()\fR more memory than a system-specific limit will fail.
80 Upon successful completion, the \fBmlock()\fR and \fBmunlock()\fR functions
81 return \fB0\fR. Otherwise, no changes are made to any locks in the address
82 space of the process, the functions return \fB\(mi1\fR and set \fBerrno\fR to
87 The \fBmlock()\fR and \fBmunlock()\fR functions will fail if:
94 The \fIaddr\fR argument is not a multiple of the page size as returned by
104 Addresses in the range [\fIaddr, addr + len\fR) are invalid for the address
105 space of a process, or specify one or more pages which are not mapped.
114 The system does not support this memory locking interface.
123 The {\fBPRIV_PROC_LOCK_MEMORY\fR} privilege is not asserted in the effective
124 set of the calling process.
129 The \fBmlock()\fR function will fail if:
136 Some or all of the memory identified by the range [\fIaddr, addr + len\fR)
137 could not be locked because of insufficient system resources or because of a
138 limit or resource control on locked memory.
144 Because of the impact on system resources, the use of \fBmlock()\fR and
145 \fBmunlock()\fR is restricted to users with the {\fBPRIV_PROC_LOCK_MEMORY\fR}
150 See \fBattributes\fR(5) for descriptions of the following attributes:
158 ATTRIBUTE TYPE ATTRIBUTE VALUE
160 Interface Stability Standard
168 \fBfork\fR(2), \fBmemcntl\fR(2), \fBmmap\fR(2), \fBplock\fR(3C),
169 \fBmlockall\fR(3C), \fBsysconf\fR(3C), \fBattributes\fR(5), \fBstandards\fR(5)