lkml.org 
[lkml]   [2009]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] configure HAVE_UNSTABLE_SCHED_CLOCK for SGI_SN systems
On Wed, Jan 07, 2009 at 12:16:03AM +0100, Peter Zijlstra wrote:
> >
> > But doesn't scheduler tick advance the rq->clock? Why do the others
> > need to fiddle with a remote runqueue's clock? When that cpu starts
> > taking ticks again, it will update it's rq->clock field and start the
> > processes. I guess I am a lot underinformed about the new scheduler
> > design.
>
> We try to do better than tick based time accounting these days.

But if you contain the drift to within one tick, it shouldn't be much
problem to just truncate negative deltas I would have thought? The
time between events on different CPUs is pretty fuzzy at the ns level
anyway, I think ;)



\
 
 \ /
  Last update: 2009-01-07 04:03    [W:0.254 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site