Lines Matching full:pages
18 which have been registered with it, looking for pages of identical
21 content). The amount of pages that KSM daemon scans in a single pass
25 KSM only merges anonymous (private) pages, never pagecache (file) pages.
26 KSM's merged pages were originally locked into kernel memory, but can now
27 be swapped out just like other user pages (but sharing is broken when they
45 to cancel that advice and restore unshared pages: whereupon KSM
55 cannot contain any pages which KSM could actually merge; even if
80 how many pages to scan before ksmd goes to sleep
92 specifies if pages from different NUMA nodes can be merged.
93 When set to 0, ksm merges only pages which physically reside
95 latency to access of shared pages. Systems with more nodes, at
102 when there are no ksm shared pages in the system: set run 2 to
103 unmerge pages first, then to 1 after changing
109 * set to 0 to stop ksmd from running but keep merged pages,
111 * set to 2 to stop ksmd and unmerge all pages currently merged, but
118 specifies whether empty pages (i.e. allocated pages that only
120 empty pages are merged with the kernel zero page(s) instead of
122 the performance on architectures with coloured zero pages,
125 KSM for some workloads, for example if the checksums of pages
128 effective for pages merged after the change.
151 specifies how frequently KSM checks the metadata of the pages
163 how many pages are being scanned for ksm
165 how many shared pages are being used
169 how many pages unique but repeatedly checked for merging
171 how many pages changing too fast to be placed in a tree
175 the number of KSM pages that hit the ``max_page_sharing`` limit
177 number of duplicated KSM pages
179 how many zero pages that are still mapped into processes were mapped by
183 ``ksm_zero_pages`` represents the actual number of pages saved by KSM.
199 KSM can save memory by merging identical pages, but also can consume
201 save each scanned page's brief rmap information. Some of these pages may