Today's scheduler statistics are using nanosecond instead of millisecond. Because of this issue, lots of tools use a wrong time unit in their code. For example, below website referred by this document uses ms in their tools, but it should be ns. http://eaglet.rain.com/rick/linux/schedstat/v12/latency.c Signed-off-by: Yong Yang <yangoliver@xxxxxxxxx> --- Documentation/scheduler/sched-stats.txt | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/Documentation/scheduler/sched-stats.txt b/Documentation/scheduler/sched-stats.txt index 8259b34..580e5e9 100644 --- a/Documentation/scheduler/sched-stats.txt +++ b/Documentation/scheduler/sched-stats.txt @@ -48,9 +48,8 @@ Next two are try_to_wake_up() statistics: 6) # of times try_to_wake_up() was called to wake up the local cpu Next three are statistics describing scheduling latency: - 7) sum of all time spent running by tasks on this processor (in jiffies) - 8) sum of all time spent waiting to run by tasks on this processor (in - jiffies) + 7) sum of all time spent running by tasks on this processor (in ns) + 8) sum of all time spent waiting to run by tasks on this processor (in ns) 9) # of timeslices run on this cpu @@ -143,8 +142,8 @@ of idleness (idle, busy, and newly idle): schedstats also adds a new /proc/<pid>/schedstat file to include some of the same information on a per-process level. There are three fields in this file correlating for that process to: - 1) time spent on the cpu - 2) time spent waiting on a runqueue + 1) time spent on the cpu (in ns) + 2) time spent waiting on a runqueue (in ns) 3) # of timeslices run on this cpu A program could be easily written to make use of these extra fields to -- 2.4.0 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
