docs/vm: move numa_memory_policy.rst to Documentation/admin-guide/mm

+1 -1

Documentation/admin-guide/mm/hugetlbpage.rst

··· 220 220 resulting effect on persistent huge page allocation is as follows: 221 221 222 222 #. Regardless of mempolicy mode [see 223 - :ref:`Documentation/vm/numa_memory_policy.rst <numa_memory_policy>`], 223 + :ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`], 224 224 persistent huge pages will be distributed across the node or nodes 225 225 specified in the mempolicy as if "interleave" had been specified. 226 226 However, if a node in the policy does not contain sufficient contiguous

+1

Documentation/admin-guide/mm/index.rst

··· 24 24 hugetlbpage 25 25 idle_page_tracking 26 26 ksm 27 + numa_memory_policy 27 28 pagemap 28 29 soft-dirty 29 30 userfaultfd

+1 -1

Documentation/filesystems/proc.txt

··· 566 566 567 567 Where: 568 568 "address" is the starting address for the mapping; 569 - "policy" reports the NUMA memory policy set for the mapping (see vm/numa_memory_policy.txt); 569 + "policy" reports the NUMA memory policy set for the mapping (see Documentation/admin-guide/mm/numa_memory_policy.rst); 570 570 "mapping details" summarizes mapping data such as mapping type, page usage counters, 571 571 node locality page counters (N0 == node0, N1 == node1, ...) and the kernel page 572 572 size, in KB, that is backing the mapping up.

+3 -2

Documentation/filesystems/tmpfs.txt

··· 105 105 NUMA memory allocation policies have optional flags that can be used in 106 106 conjunction with their modes. These optional flags can be specified 107 107 when tmpfs is mounted by appending them to the mode before the NodeList. 108 - See Documentation/vm/numa_memory_policy.rst for a list of all available 109 - memory allocation policy mode flags and their effect on memory policy. 108 + See Documentation/admin-guide/mm/numa_memory_policy.rst for a list of 109 + all available memory allocation policy mode flags and their effect on 110 + memory policy. 110 111 111 112 =static is equivalent to MPOL_F_STATIC_NODES 112 113 =relative is equivalent to MPOL_F_RELATIVE_NODES

-2

Documentation/vm/00-INDEX

··· 22 22 - a note about clearing pte/pmd and mmu notifications 23 23 numa.rst 24 24 - information about NUMA specific code in the Linux vm. 25 - numa_memory_policy.rst 26 - - documentation of concepts and APIs of the 2.6 memory policy support. 27 25 overcommit-accounting.rst 28 26 - description of the Linux kernels overcommit handling modes. 29 27 page_frags.rst

-1

Documentation/vm/index.rst

··· 14 14 :maxdepth: 1 15 15 16 16 ksm 17 - numa_memory_policy 18 17 transhuge 19 18 swap_numa 20 19 zswap

+1 -1

Documentation/vm/numa.rst

··· 110 110 such as taskset(1) and numactl(1), and program interfaces such as 111 111 sched_setaffinity(2). Further, one can modify the kernel's default local 112 112 allocation behavior using Linux NUMA memory policy. 113 - [see Documentation/vm/numa_memory_policy.rst.] 113 + [see Documentation/admin-guide/mm/numa_memory_policy.rst.] 114 114 115 115 System administrators can restrict the CPUs and nodes' memories that a non- 116 116 privileged user can specify in the scheduling or NUMA commands and functions

Documentation/vm/numa_memory_policy.rst Documentation/admin-guide/mm/numa_memory_policy.rst