docs/mm: remove useless markup

It is enough to use a file name to cross-reference another rst document.

Jon says:
  The right things will happen in the HTML output, readers of the
  plain-text will know immediately where to go, and we don't have to add
  the label clutter.

Drop reference markup and unnecessary labels and use plain file names.

Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
Link: https://lore.kernel.org/r/20230201094156.991542-3-rppt@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Mike Rapoport (IBM) 2023-02-01 11:41:55 +02:00 committed by Jonathan Corbet
parent 353c7dd636
commit ee86588960
27 changed files with 9 additions and 57 deletions

View File

@ -1,5 +1,3 @@
.. _active_mm:
========= =========
Active MM Active MM
========= =========

View File

@ -1,7 +1,5 @@
.. SPDX-License-Identifier: GPL-2.0 .. SPDX-License-Identifier: GPL-2.0
.. _arch_page_table_helpers:
=============================== ===============================
Architecture Page Table Helpers Architecture Page Table Helpers
=============================== ===============================

View File

@ -1,5 +1,3 @@
.. _balance:
================ ================
Memory Balancing Memory Balancing
================ ================

View File

@ -1,5 +1,3 @@
.. _free_page_reporting:
===================== =====================
Free Page Reporting Free Page Reporting
===================== =====================

View File

@ -1,5 +1,3 @@
.. _frontswap:
========= =========
Frontswap Frontswap
========= =========

View File

@ -1,5 +1,3 @@
.. _highmem:
==================== ====================
High Memory Handling High Memory Handling
==================== ====================

View File

@ -1,5 +1,3 @@
.. _hmm:
===================================== =====================================
Heterogeneous Memory Management (HMM) Heterogeneous Memory Management (HMM)
===================================== =====================================
@ -304,7 +302,7 @@ devm_memunmap_pages(), and devm_release_mem_region() when the resources can
be tied to a ``struct device``. be tied to a ``struct device``.
The overall migration steps are similar to migrating NUMA pages within system The overall migration steps are similar to migrating NUMA pages within system
memory (see :ref:`Page migration <page_migration>`) but the steps are split memory (see Documentation/mm/page_migration.rst) but the steps are split
between device driver specific code and shared common code: between device driver specific code and shared common code:
1. ``mmap_read_lock()`` 1. ``mmap_read_lock()``

View File

@ -1,5 +1,3 @@
.. _hugetlbfs_reserve:
===================== =====================
Hugetlbfs Reservation Hugetlbfs Reservation
===================== =====================
@ -7,7 +5,7 @@ Hugetlbfs Reservation
Overview Overview
======== ========
Huge pages as described at :ref:`hugetlbpage` are typically Huge pages as described at Documentation/mm/hugetlbpage.rst are typically
preallocated for application use. These huge pages are instantiated in a preallocated for application use. These huge pages are instantiated in a
task's address space at page fault time if the VMA indicates huge pages are task's address space at page fault time if the VMA indicates huge pages are
to be used. If no huge page exists at page fault time, the task is sent to be used. If no huge page exists at page fault time, the task is sent

View File

@ -1,5 +1,3 @@
.. hwpoison:
======== ========
hwpoison hwpoison
======== ========

View File

@ -1,5 +1,3 @@
.. _ksm:
======================= =======================
Kernel Samepage Merging Kernel Samepage Merging
======================= =======================
@ -8,7 +6,7 @@ KSM is a memory-saving de-duplication feature, enabled by CONFIG_KSM=y,
added to the Linux kernel in 2.6.32. See ``mm/ksm.c`` for its implementation, added to the Linux kernel in 2.6.32. See ``mm/ksm.c`` for its implementation,
and http://lwn.net/Articles/306704/ and https://lwn.net/Articles/330589/ and http://lwn.net/Articles/306704/ and https://lwn.net/Articles/330589/
The userspace interface of KSM is described in :ref:`Documentation/admin-guide/mm/ksm.rst <admin_guide_ksm>` The userspace interface of KSM is described in Documentation/admin-guide/mm/ksm.rst
Design Design
====== ======

View File

@ -1,7 +1,5 @@
.. SPDX-License-Identifier: GPL-2.0 .. SPDX-License-Identifier: GPL-2.0
.. _physical_memory_model:
===================== =====================
Physical Memory Model Physical Memory Model
===================== =====================

View File

@ -1,5 +1,3 @@
.. _mmu_notifier:
When do you need to notify inside page table lock ? When do you need to notify inside page table lock ?
=================================================== ===================================================

View File

@ -1,5 +1,3 @@
.. _numa:
Started Nov 1999 by Kanoj Sarcar <kanoj@sgi.com> Started Nov 1999 by Kanoj Sarcar <kanoj@sgi.com>
============= =============
@ -110,7 +108,7 @@ to improve NUMA locality using various CPU affinity command line interfaces,
such as taskset(1) and numactl(1), and program interfaces such as such as taskset(1) and numactl(1), and program interfaces such as
sched_setaffinity(2). Further, one can modify the kernel's default local sched_setaffinity(2). Further, one can modify the kernel's default local
allocation behavior using Linux NUMA memory policy. [see allocation behavior using Linux NUMA memory policy. [see
:ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`]. Documentation/admin-guide/mm/numa_memory_policy.rst].
System administrators can restrict the CPUs and nodes' memories that a non- System administrators can restrict the CPUs and nodes' memories that a non-
privileged user can specify in the scheduling or NUMA commands and functions privileged user can specify in the scheduling or NUMA commands and functions

View File

@ -1,5 +1,3 @@
.. _page_frags:
============== ==============
Page fragments Page fragments
============== ==============

View File

@ -1,5 +1,3 @@
.. _page_migration:
============== ==============
Page migration Page migration
============== ==============
@ -9,8 +7,8 @@ nodes in a NUMA system while the process is running. This means that the
virtual addresses that the process sees do not change. However, the virtual addresses that the process sees do not change. However, the
system rearranges the physical location of those pages. system rearranges the physical location of those pages.
Also see :ref:`Heterogeneous Memory Management (HMM) <hmm>` Also see Documentation/mm/hmm.rst for migrating pages to or from device
for migrating pages to or from device private memory. private memory.
The main intent of page migration is to reduce the latency of memory accesses The main intent of page migration is to reduce the latency of memory accesses
by moving pages near to the processor where the process accessing that memory by moving pages near to the processor where the process accessing that memory

View File

@ -1,5 +1,3 @@
.. _page_owner:
================================================== ==================================================
page owner: Tracking about who allocated each page page owner: Tracking about who allocated each page
================================================== ==================================================

View File

@ -1,7 +1,5 @@
.. SPDX-License-Identifier: GPL-2.0 .. SPDX-License-Identifier: GPL-2.0
.. _page_table_check:
================ ================
Page Table Check Page Table Check
================ ================

View File

@ -1,5 +1,3 @@
.. _remap_file_pages:
============================== ==============================
remap_file_pages() system call remap_file_pages() system call
============================== ==============================

View File

@ -1,5 +1,3 @@
.. _slub:
========================== ==========================
Short users guide for SLUB Short users guide for SLUB
========================== ==========================

View File

@ -1,5 +1,3 @@
.. _split_page_table_lock:
===================== =====================
Split page table lock Split page table lock
===================== =====================

View File

@ -1,5 +1,3 @@
.. _transhuge:
============================ ============================
Transparent Hugepage Support Transparent Hugepage Support
============================ ============================

View File

@ -1,5 +1,3 @@
.. _unevictable_lru:
============================== ==============================
Unevictable LRU Infrastructure Unevictable LRU Infrastructure
============================== ==============================

View File

@ -1,5 +1,3 @@
.. _z3fold:
====== ======
z3fold z3fold
====== ======

View File

@ -1,5 +1,3 @@
.. _zsmalloc:
======== ========
zsmalloc zsmalloc
======== ========

View File

@ -248,7 +248,7 @@ migrate_vma_finalize() 函数旨在使驱动程序更易于编写并集中跨驱
还有devm_request_free_mem_region(), devm_memremap_pages(), 还有devm_request_free_mem_region(), devm_memremap_pages(),
devm_memunmap_pages() 和 devm_release_mem_region() 当资源可以绑定到 ``struct device``. devm_memunmap_pages() 和 devm_release_mem_region() 当资源可以绑定到 ``struct device``.
整体迁移步骤类似于在系统内存中迁移 NUMA 页面(see :ref:`Page migration <page_migration>`) 整体迁移步骤类似于在系统内存中迁移 NUMA 页面(see Documentation/mm/page_migration.rst)
但这些步骤分为设备驱动程序特定代码和共享公共代码: 但这些步骤分为设备驱动程序特定代码和共享公共代码:
1. ``mmap_read_lock()`` 1. ``mmap_read_lock()``

View File

@ -15,7 +15,7 @@ Hugetlbfs 预留
概述 概述
==== ====
:ref:`hugetlbpage` 中描述的巨页通常是预先分配给应用程序使用的。如果VMA指 Documentation/mm/hugetlbpage.rst 中描述的巨页通常是预先分配给应用程序使用的。如果VMA指
示要使用巨页,这些巨页会在缺页异常时被实例化到任务的地址空间。如果在缺页异常 示要使用巨页,这些巨页会在缺页异常时被实例化到任务的地址空间。如果在缺页异常
时没有巨页存在任务就会被发送一个SIGBUS并经常不高兴地死去。在加入巨页支 时没有巨页存在任务就会被发送一个SIGBUS并经常不高兴地死去。在加入巨页支
持后不久人们决定在mmap()时检测巨页的短缺情况会更好。这个想法是,如果 持后不久人们决定在mmap()时检测巨页的短缺情况会更好。这个想法是,如果

View File

@ -76,7 +76,7 @@ Linux将系统的硬件资源划分为多个软件抽象称为“节点”。
系统管理员和应用程序设计者可以使用各种CPU亲和命令行接口如taskset(1)和numactl(1),以及程 系统管理员和应用程序设计者可以使用各种CPU亲和命令行接口如taskset(1)和numactl(1),以及程
序接口如sched_setaffinity(2)来限制任务的迁移以改善NUMA定位。此外人们可以使用 序接口如sched_setaffinity(2)来限制任务的迁移以改善NUMA定位。此外人们可以使用
Linux NUMA内存策略修改内核的默认本地分配行为。 [见 Linux NUMA内存策略修改内核的默认本地分配行为。 [见
:ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`]. Documentation/admin-guide/mm/numa_memory_policy.rst].
系统管理员可以使用控制组和CPUsets限制非特权用户在调度或NUMA命令和功能中可以指定的CPU和节点 系统管理员可以使用控制组和CPUsets限制非特权用户在调度或NUMA命令和功能中可以指定的CPU和节点
的内存。 [见 Documentation/admin-guide/cgroup-v1/cpusets.rst] 的内存。 [见 Documentation/admin-guide/cgroup-v1/cpusets.rst]