From: SeongJae Park <sj@kernel.org>
To: akpm@linux-foundation.org
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, SeongJae Park <sj@kernel.org>
Subject: [PATCH 5/5] Docs/admin-guide/mm/numaperf: increase depth of subsections
Date: Tue, 3 Jan 2023 18:07:54 +0000 [thread overview]
Message-ID: <20230103180754.129637-6-sj@kernel.org> (raw)
In-Reply-To: <20230103180754.129637-1-sj@kernel.org>
Each section of numaperf.rst has zero depth, and therefore be exposed to
the index of admin-guide/mm. Especially 'See Also' section on the index
makes the document weird. Hide the sections from the index by giving
the document a title and increasing the depth of each section.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
Documentation/admin-guide/mm/numaperf.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/admin-guide/mm/numaperf.rst b/Documentation/admin-guide/mm/numaperf.rst
index 166697325947..27868797621c 100644
--- a/Documentation/admin-guide/mm/numaperf.rst
+++ b/Documentation/admin-guide/mm/numaperf.rst
@@ -1,6 +1,9 @@
.. _numaperf:
-=============
+================
+NUMA Performance
+================
+
NUMA Locality
=============
@@ -61,7 +64,6 @@ that are CPUs and hence suitable for generic task scheduling, and
IO initiators such as GPUs and NICs. Unlike access class 0, only
nodes containing CPUs are considered.
-================
NUMA Performance
================
@@ -96,7 +98,6 @@ for the platform.
Access class 1 takes the same form but only includes values for CPU to
memory activity.
-==========
NUMA Cache
==========
@@ -170,7 +171,6 @@ The "size" is the number of bytes provided by this cache level.
The "write_policy" will be 0 for write-back, and non-zero for
write-through caching.
-========
See Also
========
--
2.25.1
prev parent reply other threads:[~2023-01-03 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 18:07 SeongJae Park
2023-01-03 18:07 ` [PATCH 1/5] MAINTAINERS: add types to akpm/mm git trees entries SeongJae Park
2023-01-03 18:07 ` [PATCH 2/5] MAINTAINERS/MEMORY MANAGEMENT: Add tools/vm/ as managed files SeongJae Park
2023-01-03 18:07 ` [PATCH 3/5] tools/vm: rename tools/vm to tools/mm SeongJae Park
2023-01-03 18:07 ` [PATCH 4/5] selftests/vm: rename selftets/vm to selftests/mm SeongJae Park
2023-01-03 18:07 ` SeongJae Park [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230103180754.129637-6-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).