docs/mm: Physical Memory: remove useless markup

Jon says:

  > +See also :ref:`Page Reclaim <page_reclaim>`.

  Can also just be "See also Documentation/mm/page_reclaim.rst".  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.

Remove reference markup and unnecessary labes and use plain file names.

Fixes: 5d8c5e430a ("docs/mm: Physical Memory: add structure, introduction and nodes description")
Suggested-by: Jonathan Corbet <corbet@lwn.net>
Acked-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
Link: https://lore.kernel.org/r/20230201094156.991542-2-rppt@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Mike Rapoport (IBM) 2023-02-01 11:41:54 +02:00 committed by Jonathan Corbet
parent 7c84156410
commit 353c7dd636
3 changed files with 6 additions and 10 deletions

View File

@ -1,5 +1,3 @@
.. _dma_api:
============================================ ============================================
Dynamic DMA mapping using the generic device Dynamic DMA mapping using the generic device
============================================ ============================================

View File

@ -1,7 +1,5 @@
.. SPDX-License-Identifier: GPL-2.0 .. SPDX-License-Identifier: GPL-2.0
.. _page_reclaim:
============ ============
Page Reclaim Page Reclaim
============ ============

View File

@ -39,8 +39,8 @@ one of the types described below.
* ``ZONE_DMA`` and ``ZONE_DMA32`` historically represented memory suitable for * ``ZONE_DMA`` and ``ZONE_DMA32`` historically represented memory suitable for
DMA by peripheral devices that cannot access all of the addressable DMA by peripheral devices that cannot access all of the addressable
memory. For many years there are better more and robust interfaces to get memory. For many years there are better more and robust interfaces to get
memory with DMA specific requirements (:ref:`DMA API <dma_api>`), but memory with DMA specific requirements (Documentation/core-api/dma-api.rst),
``ZONE_DMA`` and ``ZONE_DMA32`` still represent memory ranges that have but ``ZONE_DMA`` and ``ZONE_DMA32`` still represent memory ranges that have
restrictions on how they can be accessed. restrictions on how they can be accessed.
Depending on the architecture, either of these zone types or even they both Depending on the architecture, either of these zone types or even they both
can be disabled at build time using ``CONFIG_ZONE_DMA`` and can be disabled at build time using ``CONFIG_ZONE_DMA`` and
@ -64,9 +64,9 @@ one of the types described below.
change, their content may move between different physical pages. Often change, their content may move between different physical pages. Often
``ZONE_MOVABLE`` is populated during memory hotplug, but it may be ``ZONE_MOVABLE`` is populated during memory hotplug, but it may be
also populated on boot using one of ``kernelcore``, ``movablecore`` and also populated on boot using one of ``kernelcore``, ``movablecore`` and
``movable_node`` kernel command line parameters. See :ref:`Page migration ``movable_node`` kernel command line parameters. See
<page_migration>` and :ref:`Memory Hot(Un)Plug <admin_guide_memory_hotplug>` Documentation/mm/page_migration.rst and
for additional details. Documentation/admin-guide/mm/memory_hotplug.rst for additional details.
* ``ZONE_DEVICE`` represents memory residing on devices such as PMEM and GPU. * ``ZONE_DEVICE`` represents memory residing on devices such as PMEM and GPU.
It has different characteristics than RAM zone types and it exists to provide It has different characteristics than RAM zone types and it exists to provide
@ -252,7 +252,7 @@ General
Reclaim control Reclaim control
~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~
See also :ref:`Page Reclaim <page_reclaim>`. See also Documentation/mm/page_reclaim.rst.
``kswapd`` ``kswapd``
Per-node instance of kswapd kernel thread. Per-node instance of kswapd kernel thread.