Commit ee65728e authored by Mike Rapoport's avatar Mike Rapoport Committed by Andrew Morton
Browse files

docs: rename Documentation/vm to Documentation/mm



so it will be consistent with code mm directory and with
Documentation/admin-guide/mm and won't be confused with virtual machines.

Signed-off-by: default avatarMike Rapoport <rppt@linux.ibm.com>
Suggested-by: default avatarMatthew Wilcox <willy@infradead.org>
Tested-by: default avatarIra Weiny <ira.weiny@intel.com>
Acked-by: default avatarJonathan Corbet <corbet@lwn.net>
Acked-by: default avatarWu XiangCheng <bobwxc@email.cn>
parent 46a3b112
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -41,7 +41,7 @@ Description: Kernel Samepage Merging daemon sysfs interface
		sleep_millisecs: how many milliseconds ksm should sleep between
		scans.

		See Documentation/vm/ksm.rst for more information.
		See Documentation/mm/ksm.rst for more information.

What:		/sys/kernel/mm/ksm/merge_across_nodes
Date:		January 2013
+2 −2
Original line number Diff line number Diff line
@@ -37,7 +37,7 @@ Description:
		The alloc_calls file is read-only and lists the kernel code
		locations from which allocations for this cache were performed.
		The alloc_calls file only contains information if debugging is
		enabled for that cache (see Documentation/vm/slub.rst).
		enabled for that cache (see Documentation/mm/slub.rst).

What:		/sys/kernel/slab/<cache>/alloc_fastpath
Date:		February 2008
@@ -219,7 +219,7 @@ Contact: Pekka Enberg <penberg@cs.helsinki.fi>,
Description:
		The free_calls file is read-only and lists the locations of
		object frees if slab debugging is enabled (see
		Documentation/vm/slub.rst).
		Documentation/mm/slub.rst).

What:		/sys/kernel/slab/<cache>/free_fastpath
Date:		February 2008
+5 −5
Original line number Diff line number Diff line
@@ -5442,7 +5442,7 @@
			cache (risks via metadata attacks are mostly
			unchanged). Debug options disable merging on their
			own.
			For more information see Documentation/vm/slub.rst.
			For more information see Documentation/mm/slub.rst.

	slab_max_order=	[MM, SLAB]
			Determines the maximum allowed order for slabs.
@@ -5456,13 +5456,13 @@
			slub_debug can create guard zones around objects and
			may poison objects when not in use. Also tracks the
			last alloc / free. For more information see
			Documentation/vm/slub.rst.
			Documentation/mm/slub.rst.

	slub_max_order= [MM, SLUB]
			Determines the maximum allowed order for slabs.
			A high setting may cause OOMs due to memory
			fragmentation. For more information see
			Documentation/vm/slub.rst.
			Documentation/mm/slub.rst.

	slub_min_objects=	[MM, SLUB]
			The minimum number of objects per slab. SLUB will
@@ -5471,12 +5471,12 @@
			the number of objects indicated. The higher the number
			of objects the smaller the overhead of tracking slabs
			and the less frequently locks need to be acquired.
			For more information see Documentation/vm/slub.rst.
			For more information see Documentation/mm/slub.rst.

	slub_min_order=	[MM, SLUB]
			Determines the minimum page order for slabs. Must be
			lower than slub_max_order.
			For more information see Documentation/vm/slub.rst.
			For more information see Documentation/mm/slub.rst.

	slub_merge	[MM, SLUB]
			Same with slab_merge.
+1 −1
Original line number Diff line number Diff line
@@ -125,7 +125,7 @@ processor. Each bank is referred to as a `node` and for each node Linux
constructs an independent memory management subsystem. A node has its
own set of zones, lists of free and used pages and various statistics
counters. You can find more details about NUMA in
:ref:`Documentation/vm/numa.rst <numa>` and in
:ref:`Documentation/mm/numa.rst <numa>` and in
:ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`.

Page cache
+1 −1
Original line number Diff line number Diff line
@@ -4,7 +4,7 @@
Monitoring Data Accesses
========================

:doc:`DAMON </vm/damon/index>` allows light-weight data access monitoring.
:doc:`DAMON </mm/damon/index>` allows light-weight data access monitoring.
Using DAMON, users can analyze the memory access patterns of their systems and
optimize those.

Loading