Lines Matching +full:not +full:- +full:swapped

8 KSM is a memory-saving de-duplication feature, enabled by CONFIG_KSM=y,
19 content which can be replaced by a single write-protected page (which
27 be swapped out just like other user pages (but sharing is broken when they
28 are swapped back in: ksmd must rediscover their identity and merge again).
47 may suddenly require more memory than is available - possibly failing
48 with EAGAIN, but more probably arousing the Out-Of-Memory killer.
50 If KSM is not configured into the running kernel, madvise MADV_MERGEABLE
53 KSM daemon is not currently running, MADV_MERGEABLE still registers
60 will exceed ``vm.max_map_count`` (see Documentation/admin-guide/sysctl/vm.rst).
65 and might fail with EAGAIN if not enough memory for internal structures.
145         memory operations. The scheduler latency of other tasks not
147         traversal is not affected by this parameter as these
155         scan. It's a noop if not a single KSM page hit the
202 be merged, but some may not be abled to be merged after being checked
205 1) How to determine whether KSM save memory or consume memory in system-wide
208 	general_profit =~ ksm_saved_pages * sizeof(page) - (all_rmap_items) *
219 	process_profit =~ ksm_saved_pages * sizeof(page) -
229 ``ksm_merging_pages`` means a bad madvise-applied policy, so developers or
232 separately 32B on 32-bit CPU architecture and 64B on 64-bit CPU architecture.
233 so if the ``ksm_rmap_items/ksm_merging_pages`` ratio exceeds 64 on 64-bit CPU
234 or exceeds 128 on 32-bit CPU, then the app's madvise policy should be dropped,
253 	cannot do all the locking needed to reconstitute a cross-anon_vma KSM page.
255 --