lkml.org 
[lkml]   [2018]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] sched/cputime: Ensure correct utime and stime proportion
On Wed, Jun 27, 2018 at 08:22:42PM +0800, Xunlei Pang wrote:
> tick-based whole utime is utime_0, tick-based whole stime
> is stime_0, scheduler time is rtime_0.

> For a long time, the process runs mainly in userspace with
> run-sleep patterns, and because two different clocks, it
> is possible to have the following condition:
> rtime_0 < utime_0 (as with little stime_0)

I don't follow... what?

Why are you, and why do you think it makes sense to, compare rtime_0
against utime_0 ?

The [us]time_0 are, per your earlier definition, ticks. They're not an
actual measure of time. Do not compare the two, that makes no bloody
sense.

\
 
 \ /
  Last update: 2018-07-05 12:47    [W:0.097 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site