* Jeremy Fitzhardinge <[email protected]> wrote:
> > /*
> > - * Monotonic_clock - returns # of nanoseconds passed since time_init()
> > + * Scheduler clock - returns current time in nanosec units.
> > + * Now based on virtual cpu time to only account time the guest
> > + * was actually running.
>
> Runn*ing*? Does it include time the VCPU spends idle/blocked? If
> not, then the scheduler won't be able to tell how long a process has
> been asleep. Maybe this doesn't matter (I had this problem in a
> version of Xen's sched_clock, and I can't say I saw an ill effects
> from it).
CFS does measure time elapsed across task-sleep periods (and does
something similar to what the old scheduler's 'sleep average'
interactivity mechanism did), but that mechanism measures "time spent
running during sleep", not "time spent idling".
still, CFS needs time measurement across idle periods as well, for
another purpose: to be able to do precise task statistics for /proc.
(for top, ps, etc.) So it's still true that sched_clock() should include
idle periods too.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
