nanosleep() uses CLOCK_MONOTONIC, should be CLOCK_REALTIME?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: lkml <linux-kernel@...>
Cc: Thomas Gleixner <tglx@...>, john stultz <johnstul@...>, Ingo Molnar <mingo@...>, Roman Zippel <zippel@...>
Date: Sunday, June 22, 2008 - 3:35 am

Thomas,

(I gues you are the right target for this?)

The POSIX.1 specification of nanosleep() says:

        But, except for the case of being interrupted by a signal, the
        suspension time shall not be less than the time  specified  by
        rqtp, as measured by the system clock CLOCK_REALTIME.


However, reading kernel/hrtimer.c:sys_nanosleep(), it appears that
CLOCK_MONOTONIC is used.

     return hrtimer_nanosleep(&tu, rmtp, HRTIMER_MODE_REL, CLOCK_MONOTONIC);

Is there a reason to use CLOCK_MONOTONIC, instead of CLOCK_REALTIME?  Is it
intentional?  If yes, then I should document this in the man-pages.  If not,
then it should be fixed.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages onlne: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html

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

Messages in current thread:
nanosleep() uses CLOCK_MONOTONIC, should be CLOCK_REALTIME?, Michael Kerrisk, (Sun Jun 22, 3:35 am)