[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1173904438.3101.92.camel@imap.mvista.com>
Date: Wed, 14 Mar 2007 13:33:58 -0700
From: Daniel Walker <dwalker@...sta.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: john stultz <johnstul@...ibm.com>, Andi Kleen <ak@...e.de>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Con Kolivas <kernel@...ivas.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Zachary Amsden <zach@...are.com>,
James Morris <jmorris@...ei.org>,
Chris Wright <chrisw@...s-sol.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
cpufreq@...ts.linux.org.uk,
Virtualization Mailing List <virtualization@...ts.osdl.org>,
Peter Chubb <peterc@...ato.unsw.edu.au>
Subject: Re: Stolen and degraded time and schedulers
On Wed, 2007-03-14 at 12:44 -0700, Jeremy Fitzhardinge wrote:
> Daniel Walker wrote:
> > sched_clock is used to bank real time against some specific states
> > inside the scheduler, and no it doesn't _just_ measure a processes
> > executing time.
> >
>
> Could you point these places out? All uses of sched_clock() that I
> could see in kernel/sched.c seemed to be related to working out how
> long
> something spent executing, either in the scheduler proper, or
> benchmarking cache characteristics.
For interactive tasks (basic scheduling) the execution time, and sleep
time need to be measured. It's also used for some posix cpu timers
(sched_ns) , and it used for migration thread initialization. I'm sure
it's used for a variety of out-of-tree random timing as well..
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists