public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: xunlei <xunlei.pang@gmail.com>
Cc: Xunlei Pang <xlpang@linux.alibaba.com>,
	Ingo Molnar <mingo@redhat.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Tejun Heo <tj@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/cputime: Ensure correct utime and stime proportion
Date: Mon, 9 Jul 2018 12:47:59 +0200	[thread overview]
Message-ID: <20180709104759.GJ2476@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <da032f2b-61e0-bd12-f0ec-0ef21b87d3d7@gmail.com>

On Thu, Jul 05, 2018 at 09:58:50PM +0800, xunlei wrote:
> It is rtime < utime + stime, that is the imprecise tick-based run time
> may be larger than precise sum_exec_runtime scheduler-based run time, it
> can happen with some frequent run-sleep patterns.

You're still comparing two values that should not be compared. utime +
stime is not a run-time. You _CANNOT_ compare to rtime and doing so
means you're still not getting it.


  reply	other threads:[~2018-07-09 10:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  7:15 [PATCH] sched/cputime: Ensure correct utime and stime proportion Xunlei Pang
2018-06-22 10:35 ` kbuild test robot
2018-06-25  8:14   ` Xunlei Pang
2018-06-26 12:19 ` Xunlei Pang
2018-06-26 15:49   ` Peter Zijlstra
2018-06-27 12:22     ` Xunlei Pang
2018-07-05 10:46       ` Peter Zijlstra
2018-07-05 13:21         ` Xunlei Pang
2018-07-05 13:42           ` Peter Zijlstra
2018-07-05 13:58             ` xunlei
2018-07-09 10:47               ` Peter Zijlstra [this message]
2018-07-09  5:52           ` Xunlei Pang
2018-07-09 10:48             ` Peter Zijlstra
2018-07-09 15:00               ` Xunlei Pang
2018-07-02 15:21     ` Tejun Heo
2018-07-04  6:56       ` Xunlei Pang

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=20180709104759.GJ2476@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tj@kernel.org \
    --cc=xlpang@linux.alibaba.com \
    --cc=xunlei.pang@gmail.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