All of lore.kernel.org
 help / color / mirror / Atom feed
From: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
To: Frederic Weisbecker <frederic@kernel.org>,
	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>
Cc: "'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: Wed, 21 Jul 2021 08:24:04 +0000	[thread overview]
Message-ID: <OSBPR01MB2183EDD7935603BDD26825D3EBE39@OSBPR01MB2183.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20210628141300.GA5710@lothringen>

Hi Frederic

> > 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.

I'm looking forward to posting your patch.
Do you have a specific plan? I would like to know the rough period
until this correction is made.

Thanks.
Hitomi Hasegawa

  reply	other threads:[~2021-07-21  8:39 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
2021-07-21  8:24                 ` hasegawa-hitomi [this message]
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=OSBPR01MB2183EDD7935603BDD26825D3EBE39@OSBPR01MB2183.jpnprd01.prod.outlook.com \
    --to=hasegawa-hitomi@fujitsu.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=frederic@kernel.org \
    --cc=fweisbec@gmail.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 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.