Differences

This shows you the differences between two versions of the page.

--- realtime:documentation:howto:applications:memory [2017/07/15 01:55]
jithu [Memory Locking]
+++ realtime:documentation:howto:applications:memory [2017/07/15 01:56]
jithu [Memory Locking]
@@ Line 8: / Line 8: @@
 ===== Memory Locking =====
 Memory locking APIs allow an application to instruct the kernel to associate (some or all of its) virtual memory pages with real page frames and keep it that way. In other words :
-  * Memory locking calls will trigger the necessary page-faults to bring in the pages being locked to physical memory and populates the application's page-table with the corresponding entries. Consequently first access to a locked-memory (following an ''mlock*()'' call) will already have physical memory assigned and will not page fault (in  RT-critical path) thus removing the need to explicitly pre-fault the memory otherwise.
+  * Memory locking APIs will trigger the necessary page-faults to bring in the pages being locked to physical memory and populates the application's page-table with the corresponding entries. Consequently first access to a locked-memory (following an ''mlock*()'' call) will already have physical memory assigned and will not page fault (in  RT-critical path) thus removing the need to explicitly pre-fault the memory otherwise.
   * Further memory locking prevents an application's memory pages, from being paged-out, anytime during its lifetime even in when the overall system is facing memory pressure.

Wiki