Searched refs:mlockall (Results 1 – 11 of 11) sorted by relevance
23 if (mlockall(MCL_CURRENT | MCL_ONFAULT | MCL_FUTURE)) { in test_limit()
563 if (mlockall(MCL_CURRENT)) { in test_munlockall()589 if (mlockall(MCL_CURRENT | MCL_ONFAULT)) { in test_munlockall()605 if (mlockall(MCL_CURRENT | MCL_FUTURE)) { in test_munlockall()717 if (mlockall(MCL_CURRENT | MCL_ONFAULT | MCL_FUTURE)) { in test_mlockall()
144 mlockall(MCL_CURRENT|MCL_FUTURE); in main()
21 - mlock()/mlockall() system call handling.277 (1) in the mlock()/mlockall() system call handlers;282 (3) mmapping a region in a task that has called mlockall() with the MCL_FUTURE307 mlock()/mlockall() SYSTEM CALL HANDLING310 Both [do_]mlock() and [do_]mlockall() system call handlers call mlock_fixup()311 for each VMA in the range specified by the call. In the case of mlockall(),387 do_mlock[all]() - as the mlock() and mlockall() system calls with the unlock vs468 In addition the mlock()/mlockall() system calls, an application can request477 task that has previously called mlockall() with the MCL_FUTURE flag will result574 mlockall(), overall this is a fairly rare event.
240 ENTRY_SAME(mlockall)
159 SYSCALL_SPU(mlockall)
721 SYSCALL_DEFINE1(mlockall, int, flags) in SYSCALL_DEFINE1() argument
160 151 common mlockall sys_mlockall
161 152 i386 mlockall sys_mlockall
141 preferably using mlockall(), before calling SNAPSHOT_FREEZE.
329 helpful, especially when combined with the mlock() and mlockall()