From: YI <afctgo@gmail.com>
To: trivial@kernel.org
Cc: YI <afctgo@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>,
Kalesh Singh <kaleshsingh@google.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Colin Cross <ccross@google.com>, Mike Rapoport <rppt@kernel.org>,
Peter Xu <peterx@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [PATCH] docs: proc.rst: fix wrong time unit
Date: Thu, 3 Mar 2022 00:11:16 +0800 [thread overview]
Message-ID: <20220302161122.3984304-1-uuuuuu@protonmail.com> (raw)
From: YI <afctgo@gmail.com>
Dear Trivial Patch Monkey,
This commit fixes a small documentaion problem reported in
https://bugzilla.kernel.org/show_bug.cgi?id=194593.
Some fields in the file /proc/$pid/stat represent time.
Their units are clock_t, not jiffies as stated in the documentation.
This commit fixes https://bugzilla.kernel.org/show_bug.cgi?id=194593.
Reported-by: hujunjie
Signed-off-by: YI <afctgo@gmail.com>
---
Documentation/filesystems/proc.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 061744c436d9..433ad4623630 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -340,10 +340,10 @@ It's slow but very precise.
cmin_flt number of minor faults with child's
maj_flt number of major faults
cmaj_flt number of major faults with child's
- utime user mode jiffies
- stime kernel mode jiffies
- cutime user mode jiffies with child's
- cstime kernel mode jiffies with child's
+ utime user mode processor time (clock_t)
+ stime kernel mode processor time (clock_t)
+ cutime user mode processor time (clock_t) with child's
+ cstime kernel mode processor time (clock_t) with child's
priority priority level
nice nice level
num_threads number of threads
@@ -370,8 +370,8 @@ It's slow but very precise.
rt_priority realtime priority
policy scheduling policy (man sched_setscheduler)
blkio_ticks time spent waiting for block IO
- gtime guest time of the task in jiffies
- cgtime guest time of the task children in jiffies
+ gtime guest time of the task in processor time (clock_t)
+ cgtime guest time of the task children in processor time (clock_t)
start_data address above which program data+bss is placed
end_data address below which program data+bss is placed
start_brk address above which program heap can be expanded with brk()
--
2.34.1
next reply other threads:[~2022-03-02 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 16:11 YI [this message]
2022-03-09 23:26 ` Jonathan Corbet
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=20220302161122.3984304-1-uuuuuu@protonmail.com \
--to=afctgo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ccross@google.com \
--cc=corbet@lwn.net \
--cc=kaleshsingh@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@christoph.anton.mitterer.name \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=trivial@kernel.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®