Messages in this thread | | | Date | Sun, 7 May 2006 13:43:07 +0100 | From | Russell King <> | Subject | Re: sched_clock() uses are broken |
| |
On Sun, May 07, 2006 at 10:33:41PM +1000, Nick Piggin wrote: > Mike Galbraith wrote: > >On Wed, 2006-05-03 at 03:07 +1000, Nick Piggin wrote: > > > >>Other problem is that some people didn't RTFM and have started trying to > >>use it for precise accounting :( > > > > > >Are you talking about me perchance? I don't really care about precision > >_that_ much, though I certainly do want to tighten timeslice accounting. > > No, sched_clock is fine to be used in CPU scheduling choices, which are > heuristic anyway (although strictly speaking, even using it for timeslicing > within a single CPU could cause slight unfairness).
Except maybe if it rolls over every 178 seconds, which is my original point. Maybe someone could comment on my initial patch sent 5 days ago?
-- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |