lkml.org 
[lkml]   [2019]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 3/9] docs: Remove unnecessary reference link title
    Date
    Labels that precede a heading use the heading as the link title.
    Explicitly adding the link title defeats the purpose of this feature
    i.e. makes the reference less maintainable.

    Remove unnecessary reference link title.

    Signed-off-by: Tobin C. Harding <tobin@kernel.org>
    ---
    Documentation/admin-guide/mm/numa_memory_policy.rst | 9 ++++-----
    1 file changed, 4 insertions(+), 5 deletions(-)

    diff --git a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst
    index d78c5b315f72..1ef0146eaa4d 100644
    --- a/Documentation/admin-guide/mm/numa_memory_policy.rst
    +++ b/Documentation/admin-guide/mm/numa_memory_policy.rst
    @@ -20,8 +20,7 @@ which is an administrative mechanism for restricting the nodes from which
    memory may be allocated by a set of processes. Memory policies are a
    programming interface that a NUMA-aware application can take advantage of. When
    both cpusets and policies are applied to a task, the restrictions of the cpuset
    -takes priority. See :ref:`Memory Policies and cpusets <mem_pol_and_cpusets>`
    -below for more details.
    +takes priority. See :ref:`mem_pol_and_cpusets` below for more details.

    Memory Policy Concepts
    ======================
    @@ -56,7 +55,7 @@ Task/Process Policy
    [clone() w/o the CLONE_VM flag] and exec*(). This allows a parent task
    to establish the task policy for a child task exec()'d from an
    executable image that has no awareness of memory policy. See the
    - :ref:`Memory Policy APIs <memory_policy_apis>` section,
    + :ref:`memory_policy_apis` section,
    below, for an overview of the system call
    that a task may use to set/change its task/process policy.

    @@ -77,7 +76,7 @@ VMA Policy
    A "VMA" or "Virtual Memory Area" refers to a range of a task's
    virtual address space. A task may define a specific policy for a range
    of its virtual address space. See the
    - :ref:`Memory Policy APIs <memory_policy_apis>` section,
    + :ref:`memory_policy_apis` section,
    below, for an overview of the mbind() system call used to set a VMA
    policy.

    @@ -142,7 +141,7 @@ Shared Policy
    Although hugetlbfs segments now support lazy allocation, their support
    for shared policy has not been completed.

    - As mentioned above in :ref:`VMA policies <vma_policy>` section,
    + As mentioned above in :ref:`vma_policy` section,
    allocations of page cache pages for regular files mmap()ed
    with MAP_SHARED ignore any VMA policy installed on the virtual
    address range backed by the shared file mapping. Rather,
    --
    2.21.0
    \
     
     \ /
      Last update: 2019-03-07 22:13    [W:4.257 / U:0.424 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site