From: Frederic Weisbecker <frederic@kernel.org>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"'mgorman@suse.de'" <mgorman@suse.de>,
"'mingo@kernel.org'" <mingo@kernel.org>,
"'tglx@linutronix.de'" <tglx@linutronix.de>,
"'juri.lelli@redhat.com'" <juri.lelli@redhat.com>,
"'vincent.guittot@linaro.org'" <vincent.guittot@linaro.org>,
"'fweisbec@gmail.com'" <fweisbec@gmail.com>,
"'dietmar.eggemann@arm.com'" <dietmar.eggemann@arm.com>,
"'rostedt@goodmis.org'" <rostedt@goodmis.org>,
"'bsegall@google.com'" <bsegall@google.com>,
"'bristot@redhat.com'" <bristot@redhat.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Utime and stime are less when getrusage (RUSAGE_THREAD) is executed on a tickless CPU.
Date: Mon, 28 Jun 2021 16:13:00 +0200 [thread overview]
Message-ID: <20210628141300.GA5710@lothringen> (raw)
In-Reply-To: <OSBPR01MB2183D3C6B2BBF25B22DD09FAEB039@OSBPR01MB2183.jpnprd01.prod.outlook.com>
On Mon, Jun 28, 2021 at 02:36:27AM +0000, hasegawa-hitomi@fujitsu.com wrote:
> Hi Frederic, Peter, and Mel
>
> > I tested this and confirmed that it gives accurate values.
> > Also, task_sched_runtime () is done only on nohz_full CPU, so I think
> > it's a better idea than before.
> > I hope you will incorporate this fix into your mainline.
>
> I have also confirmed that CPUs other than nohz_full have very little overhead.
> Please consider merging it into the mainline.
Ok, I'm going to submit a proper patch.
Thanks!
next prev parent reply other threads:[~2021-06-28 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 3:28 Utime and stime are less when getrusage (RUSAGE_THREAD) is executed on a tickless CPU hasegawa-hitomi
2021-05-18 7:59 ` hasegawa-hitomi
2021-05-18 8:23 ` Peter Zijlstra
2021-05-19 6:30 ` hasegawa-hitomi
2021-05-19 9:24 ` Peter Zijlstra
2021-05-19 9:28 ` Peter Zijlstra
2021-05-21 6:40 ` hasegawa-hitomi
2021-05-21 8:41 ` Mel Gorman
2021-06-16 2:27 ` hasegawa-hitomi
2021-06-16 12:31 ` Frederic Weisbecker
2021-06-16 12:54 ` Frederic Weisbecker
2021-06-22 6:49 ` hasegawa-hitomi
2021-06-28 2:36 ` hasegawa-hitomi
2021-06-28 14:13 ` Frederic Weisbecker [this message]
2021-07-21 8:24 ` hasegawa-hitomi
2021-08-31 4:18 ` hasegawa-hitomi
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=20210628141300.GA5710@lothringen \
--to=frederic@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=fweisbec@gmail.com \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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