From: Jonathan Corbet <corbet@lwn.net>
To: Jui-Tse Huang <juitse.huang@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Valentin Schneider <valentin.schneider@arm.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Huaixin Chang <changhuaixin@linux.alibaba.com>,
Beata Michalska <beata.michalska@arm.com>,
Chun-Hung Tseng <henrybear327@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jui-Tse Huang <juitse.huang@gmail.com>,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>
Subject: Re: [PATCH] docs/scheduler: fix unit error
Date: Sat, 16 Apr 2022 02:55:16 -0600 [thread overview]
Message-ID: <87ilr92yrv.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220415033618.15655-1-juitse.huang@gmail.com>
Jui-Tse Huang <juitse.huang@gmail.com> writes:
> The unit mentioned in the documentation of scheduler statistics is
> outdated which may mislead the readers.
>
> The unit of statistics that is reported by /proc/schedstat is modified
> to nanosecond, and the unit of statistics that is reported by
> /proc/PID/schedstat is provided as well to make the context consistent.
>
> The rq_cpu_time and the rq_sched_info.run_delay of a run queue, and the
> sched_info.run_delay of a task are all updated based on the clock of the
> run queue, while the se.sum_exec_runtime of a task is updated based on
> the clock_task of the run queue of the task. Both the clock and
> clock_task are relied on the return value of the function sched_clock()
> which is in the unit of nanosecond.
>
> Signed-off-by: Jui-Tse Huang <juitse.huang@gmail.com>
> ---
> Documentation/scheduler/sched-stats.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Part of this had already been fixed by a previous patch, but git was
able to figure it out...this one's applied as well, thanks.
jon
prev parent reply other threads:[~2022-04-16 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 3:36 Jui-Tse Huang
2022-04-16 8:55 ` Jonathan Corbet [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=87ilr92yrv.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=beata.michalska@arm.com \
--cc=changhuaixin@linux.alibaba.com \
--cc=henrybear327@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=juitse.huang@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
/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®