Valdis.Kletnieks@xxxxxx wrote: > On Wed, 01 Dec 2010 10:43:59 GMT, Jamie Lokier said: > > > So maybe CLOCK_MONOTONIC should be changed to include elapsed time > > during suspend/resume, and CLOCK_MONOTONIC_RAW could remain as it is, > > for programs that want that? > > Wouldn't that be an API break for programs that are expecting the current > behavior of CLOCK_MONOTONIC? Yes, there should be a way to request either of > them - but if there's only one way now, it should continue to act the current > way, and the added way is the second option. I don't know. Can you think of any program which would break if suspend/resume's clocks behaved like ordinary task scheduling - when a task doesn't run for a long time because of scheduling decisions? Hmm, I guess some realtime apps might like to know. Currently CLOCK_MONOTONIC jumps forwards by 4 seconds on suspend/resume anyway (as seen by userspace), on my x86 laptop running 2.6.37-rc3. So it does already jump a bit... But see my other reply; maybe there's no need to change it. A reliable, immediate notification that CLOCK_MONOTONIC's relationship to real time has been disrupted by an unknown amount would be sufficient for the problems I have in mind. -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
