All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: nanosleep() uses CLOCK_MONOTONIC, should be CLOCK_REALTIME?
Date: Sun, 22 Jun 2008 09:35:41 +0200	[thread overview]
Message-ID: <485E00CD.9060503@gmail.com> (raw)

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


             reply	other threads:[~2008-06-23  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22  7:35 Michael Kerrisk [this message]
2008-06-23  8:34 ` nanosleep() uses CLOCK_MONOTONIC, should be CLOCK_REALTIME? Bart Van Assche
2008-06-23  9:48   ` Michael Kerrisk
2008-06-23 11:56     ` Bart Van Assche
2008-06-24  5:08       ` Michael Kerrisk
2008-06-24  5:18       ` Michael Kerrisk
2008-06-23 12:43     ` Roman Zippel
2008-06-24  5:39       ` Michael Kerrisk
2008-06-24  8:01         ` Bart Van Assche
2008-06-24  8:27           ` Michael Kerrisk
2008-06-24  9:27             ` Bart Van Assche
2008-06-24  9:31               ` Michael Kerrisk
2008-06-25  6:13         ` Thomas Gleixner
2008-06-25  6:16           ` Michael Kerrisk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=485E00CD.9060503@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.