From: Haowen Bai <baihaowen@meizu.com>
To: <baihaowen@meizu.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion
Date: Mon, 25 Apr 2022 15:32:11 +0800 [thread overview]
Message-ID: <1650871931-10015-3-git-send-email-baihaowen@meizu.com> (raw)
In-Reply-To: <1650871931-10015-1-git-send-email-baihaowen@meizu.com>
After make htmldocs, the table which is made of tab will
display all by one line. so we make a standard table for STANDARD
FORMAT SPECIFIERS description.
Signed-off-by: Haowen Bai <baihaowen@meizu.com>
---
Documentation/vm/page_owner.rst | 34 ++++++++++++++++++++--------------
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/Documentation/vm/page_owner.rst b/Documentation/vm/page_owner.rst
index 422d5fa99e84..a8505e3a3044 100644
--- a/Documentation/vm/page_owner.rst
+++ b/Documentation/vm/page_owner.rst
@@ -174,22 +174,28 @@ STANDARD FORMAT SPECIFIERS
For --sort option:
- KEY LONG DESCRIPTION
- p pid process ID
- tg tgid thread group ID
- n name task command name
- st stacktrace stack trace of the page allocation
- T txt full text of block
- ft free_ts timestamp of the page when it was released
- at alloc_ts timestamp of the page when it was allocated
+ ==== ========== ============================================
+ KEY LONG DESCRIPTION
+ ==== ========== ============================================
+ p pid process ID
+ tg tgid thread group ID
+ n name task command name
+ st stacktrace stack trace of the page allocation
+ T txt full text of block
+ ft free_ts timestamp of the page when it was released
+ at alloc_ts timestamp of the page when it was allocated
ator allocator memory allocator for pages
+ ==== ========== ============================================
For --curl option:
- KEY LONG DESCRIPTION
- p pid process ID
- tg tgid thread group ID
- n name task command name
- f free whether the page has been released or not
- st stacktrace stack trace of the page allocation
+ ==== =========== ============================================
+ KEY LONG DESCRIPTION
+ ==== =========== ============================================
+ p pid process ID
+ tg tgid thread group ID
+ n name task command name
+ f free whether the page has been released or not
+ st stacktrace stack trace of the page allocation
ator allocator memory allocator for pages
+ ==== =========== ============================================
--
2.7.4
next prev parent reply other threads:[~2022-04-25 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 7:32 [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst Haowen Bai
2022-04-25 7:32 ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
2022-04-25 16:57 ` Jonathan Neuschäfer
2022-04-25 7:32 ` Haowen Bai [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 7:07 [PATCH 0/2] " Haowen Bai
2022-04-26 7:07 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
[not found] <1650956694-30699-1-git-send-email-baihaowen@meizu.com>
2022-04-26 7:04 ` Haowen Bai
2022-04-19 14:42 [PATCH V8] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst yanteng si
2022-04-20 3:06 ` [PATCH 0/2] " Haowen Bai
2022-04-20 3:06 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
2022-04-20 12:31 ` Bagas Sanjaya
2022-04-20 12:46 ` Jonathan Corbet
2022-04-24 3:38 ` Akira Yokosawa
2022-04-24 5:24 ` Jonathan Corbet
2022-04-26 8:39 ` Alex Shi
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=1650871931-10015-3-git-send-email-baihaowen@meizu.com \
--to=baihaowen@meizu.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.