Lines Matching +full:software +full:- +full:locked

13 .\"    may be used to endorse or promote products derived from this software
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
55 system call unlocks pages previously locked by one or more
69 system call, the indicated pages will cause neither a non-resident page
70 nor address-translation fault until they are unlocked.
71 They may still cause protection-violation faults or TLB-miss faults on
72 architectures with software-managed TLBs.
73 The physical pages remain in memory until all locked mappings for the pages
75 Multiple processes may have the same physical pages locked via their own
77 A single process may likewise have pages multiply-locked via different virtual
84 Locked mappings are not inherited by the child process after a
91 is limited by both the per-process
94 system-wide
107 is set to 0 these calls are only available to the super-user.
109 .Rv -std
111 If the call succeeds, all pages in the range become locked (unlocked);
112 otherwise the locked status of all pages in the range remains unchanged.
118 .Bl -tag -width Er
121 is set to 0 and the caller is not the super-user.
127 Locking the indicated range would exceed the per-process or system-wide limits
128 for locked memory.
134 .Bl -tag -width Er
137 is set to 0 and the caller is not the super-user.
166 Allocating too much wired memory can lead to a memory-allocation deadlock
169 The per-process and system-wide resource limits of locked memory apply
170 to the amount of virtual memory locked, not the amount of locked physical
172 Hence two distinct locked mappings of the same physical page counts as
173 2 pages aginst the system limit, and also against the per-process limit
176 The per-process resource limit is not currently supported.