summaryrefslogtreecommitdiffstats
path: root/Documentation/vm
diff options
context:
space:
mode:
authorMike Rapoport <rppt@linux.vnet.ibm.com>2018-04-24 02:40:26 -0400
committerJonathan Corbet <corbet@lwn.net>2018-04-27 19:19:40 -0400
commit2a695ca412943b88abde5dda0d5b6876fd154ac8 (patch)
treef5c092dab193055bcbf701693ea785c89dde2511 /Documentation/vm
parent6570c785ea8fdb3c6e8f7591d25d33fd519f928b (diff)
docs/vm: ksm: update stable_node_chains_prune_millisecs description
Make the description of stable_node_chains_prune_millisecs sysfs parameter less implementation aware and add a few words about this parameter in the "Design" section. Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/vm')
-rw-r--r--Documentation/vm/ksm.rst19
1 files changed, 11 insertions, 8 deletions
diff --git a/Documentation/vm/ksm.rst b/Documentation/vm/ksm.rst
index 00961b8ab03e..18d7c710a5f3 100644
--- a/Documentation/vm/ksm.rst
+++ b/Documentation/vm/ksm.rst
@@ -150,14 +150,12 @@ max_page_sharing
150 traversals are always schedule friendly themselves. 150 traversals are always schedule friendly themselves.
151 151
152stable_node_chains_prune_millisecs 152stable_node_chains_prune_millisecs
153 How frequently to walk the whole list of stable_node "dups" 153 specifies how frequently KSM checks the metadata of the pages
154 linked in the stable_node "chains" in order to prune stale 154 that hit the deduplication limit for stale information.
155 stable_nodes. Smaller milllisecs values will free up the KSM 155 Smaller milllisecs values will free up the KSM metadata with
156 metadata with lower latency, but they will make ksmd use more 156 lower latency, but they will make ksmd use more CPU during the
157 CPU during the scan. This only applies to the stable_node 157 scan. It's a noop if not a single KSM page hit the
158 chains so it's a noop if not a single KSM page hit the 158 ``max_page_sharing`` yet.
159 ``max_page_sharing`` yet (there would be no stable_node chains in
160 such case).
161 159
162The effectiveness of KSM and MADV_MERGEABLE is shown in ``/sys/kernel/mm/ksm/``: 160The effectiveness of KSM and MADV_MERGEABLE is shown in ``/sys/kernel/mm/ksm/``:
163 161
@@ -249,6 +247,11 @@ deduplication factor at the expense of slower worst case for rmap
249walks for any KSM page which can happen during swapping, compaction, 247walks for any KSM page which can happen during swapping, compaction,
250NUMA balancing and page migration. 248NUMA balancing and page migration.
251 249
250The whole list of stable_node "dups" linked in the stable_node
251"chains" is scanned periodically in order to prune stale stable_nodes.
252The frequency of such scans is defined by
253``stable_node_chains_prune_millisecs`` sysfs tunable.
254
252Reference 255Reference
253--------- 256---------
254.. kernel-doc:: mm/ksm.c 257.. kernel-doc:: mm/ksm.c