Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e27a20f1 authored by Mike Rapoport's avatar Mike Rapoport Committed by Jonathan Corbet
Browse files

docs/admin-guide/mm: convert plain text cross references to hyperlinks 



Signed-off-by: default avatarMike Rapoport <rppt@linux.vnet.ibm.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 1ad1335d

Documentation/admin-guide/mm/hugetlbpage.rst

+2 −1
Original line number Original line Diff line number Diff line
@@ -219,7 +219,8 @@ When adjusting the persistent hugepage count via ``nr_hugepages_mempolicy``, any 
memory policy mode--bind, preferred, local or interleave--may be used.  The

memory policy mode--bind, preferred, local or interleave--may be used.  The

resulting effect on persistent huge page allocation is as follows:

resulting effect on persistent huge page allocation is as follows:





#. Regardless of mempolicy mode [see Documentation/vm/numa_memory_policy.rst],

#. Regardless of mempolicy mode [see

   :ref:`Documentation/vm/numa_memory_policy.rst <numa_memory_policy>`],

   persistent huge pages will be distributed across the node or nodes

   persistent huge pages will be distributed across the node or nodes

   specified in the mempolicy as if "interleave" had been specified.

   specified in the mempolicy as if "interleave" had been specified.

   However, if a node in the policy does not contain sufficient contiguous

   However, if a node in the policy does not contain sufficient contiguous

Documentation/admin-guide/mm/idle_page_tracking.rst

+3 −2
Original line number Original line Diff line number Diff line
@@ -65,8 +65,9 @@ workload one should: 
    are not reclaimable, he or she can filter them out using

    are not reclaimable, he or she can filter them out using

    ``/proc/kpageflags``.

    ``/proc/kpageflags``.





See Documentation/admin-guide/mm/pagemap.rst for more information about

See :ref:`Documentation/admin-guide/mm/pagemap.rst <pagemap>` for more

``/proc/pid/pagemap``, ``/proc/kpageflags``, and ``/proc/kpagecgroup``.

information about ``/proc/pid/pagemap``, ``/proc/kpageflags``, and

``/proc/kpagecgroup``.





.. _impl_details:

.. _impl_details:

Documentation/admin-guide/mm/pagemap.rst

+11 −7
Original line number Original line Diff line number Diff line
@@ -18,7 +18,8 @@ There are four components to pagemap: 
    * Bits 0-54  page frame number (PFN) if present

    * Bits 0-54  page frame number (PFN) if present

    * Bits 0-4   swap type if swapped

    * Bits 0-4   swap type if swapped

    * Bits 5-54  swap offset if swapped

    * Bits 5-54  swap offset if swapped

    * Bit  55    pte is soft-dirty (see Documentation/admin-guide/mm/soft-dirty.rst)

    * Bit  55    pte is soft-dirty (see

      :ref:`Documentation/admin-guide/mm/soft-dirty.rst <soft_dirty>`)

    * Bit  56    page exclusively mapped (since 4.2)

    * Bit  56    page exclusively mapped (since 4.2)

    * Bits 57-60 zero

    * Bits 57-60 zero

    * Bit  61    page is file-page or shared-anon (since 3.5)

    * Bit  61    page is file-page or shared-anon (since 3.5)
@@ -97,9 +98,11 @@ Short descriptions to the page flags 
    A compound page with order N consists of 2^N physically contiguous pages.

    A compound page with order N consists of 2^N physically contiguous pages.

    A compound page with order 2 takes the form of "HTTT", where H donates its

    A compound page with order 2 takes the form of "HTTT", where H donates its

    head page and T donates its tail page(s).  The major consumers of compound

    head page and T donates its tail page(s).  The major consumers of compound

    pages are hugeTLB pages (Documentation/admin-guide/mm/hugetlbpage.rst), the SLUB etc.

    pages are hugeTLB pages

    memory allocators and various device drivers. However in this interface,

    (:ref:`Documentation/admin-guide/mm/hugetlbpage.rst <hugetlbpage>`),

    only huge/giga pages are made visible to end users.

    the SLUB etc.  memory allocators and various device drivers.

    However in this interface, only huge/giga pages are made visible

    to end users.

16 - COMPOUND_TAIL

16 - COMPOUND_TAIL

    A compound page tail (see description above).

    A compound page tail (see description above).

17 - HUGE

17 - HUGE
@@ -118,9 +121,10 @@ Short descriptions to the page flags 
    zero page for pfn_zero or huge_zero page

    zero page for pfn_zero or huge_zero page

25 - IDLE

25 - IDLE

    page has not been accessed since it was marked idle (see

    page has not been accessed since it was marked idle (see

    Documentation/admin-guide/mm/idle_page_tracking.rst). Note that this flag may be

    :ref:`Documentation/admin-guide/mm/idle_page_tracking.rst <idle_page_tracking>`).

    stale in case the page was accessed via a PTE. To make sure the flag

    Note that this flag may be stale in case the page was accessed via

    is up-to-date one has to read ``/sys/kernel/mm/page_idle/bitmap`` first.

    a PTE. To make sure the flag is up-to-date one has to read

    ``/sys/kernel/mm/page_idle/bitmap`` first.





IO related page flags

IO related page flags

---------------------

---------------------