Re: [LAD] Strange gettimeofday behaviour - out of order times.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-dev@...>
Date: Thursday, May 5, 2011 - 6:16 am

On May 4, 2011 08:20:51 pm you wrote:

Weird, CLOCK_REALTIME does it too.
Only CLOCK_PROCESS_CPUTIME_ID does not.

Been reading, according to places like this:

http://stackoverflow.com/questions/3523442/difference-between-clock-real...
and-clock-monotonic

http://stackoverflow.com/questions/3657289/linux-clock-gettimeclock-mono...
strange-non-monotonic-behavior

CLOCK_MONOTONIC and CLOCK_MONOTONIC_RAW are not supposed to go backwards
but apparently CLOCK_MONOTONIC just might and CLOCK_MONOTONIC_RAW is better,
and CLOCK_REALTIME is less reliable than that.

However on that second page it mentions a kernel fix, more recent than mine.
Mine also doesn't seem to have CLOCK_MONOTONIC_RAW.

I am going to chalk it up to this older kernel, and test on my newer machine
and hope it vanishes...

In the meantime, I can make the code I'm working on tolerant.
I'm just not sure how this affects the rest of the existing app code -
could this be the source of occasional bugs or have we just been lucky or
is it already tolerant...

Thanks!

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] Strange gettimeofday behaviour - out of order times., Tim E. Real, (Thu May 5, 6:16 am)