From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Why does timerfd() only support CLOCK_REALTIME and CLOCK_MONOTONIC?
Date: Mon, 9 Feb 2009 07:25:50 +1300 [thread overview]
Message-ID: <cfd18e0f0902081025t3fe333ev1616af990e6d19ce@mail.gmail.com> (raw)
Hi Davide,
At the moment I'm looking into writing man pages for timer_create(2)
and friends. (Somewhat bizarrely, these pages do not yet exist.) As
I looked into the source code of timer_create(), etc., and did some
tests, I saw that timer_create() supports the following clocks:
TIMER_REALTIME
TIMER_MONOTONIC
TIMER_PROCESS_CPUTIME_ID
TIMER_THREAD_CPUTIME_ID
clockid obtained from clock_getcpuclockid(3)
clockid obtained from pthread_getcpuclockid(3)
On the other hand, timerfd() only permits the first two of these.
What's the reason for that limitation of timerfd()? (It may be worth
adding something to the man page on this point.)
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next reply other threads:[~2009-02-08 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 18:25 Michael Kerrisk [this message]
2009-02-08 19:29 ` Davide Libenzi
2009-02-08 20:46 ` Davide Libenzi
2009-02-08 21:18 ` Michael Kerrisk
2009-02-08 21:22 ` Davide Libenzi
2009-02-08 21:26 ` Michael Kerrisk
2009-02-08 21:29 ` Michael Kerrisk
2009-02-08 21:50 ` Davide Libenzi
2009-02-08 21:53 ` Michael Kerrisk
2009-02-08 22:06 ` Davide Libenzi
2009-02-08 22:10 ` [stable] " Greg KH
2009-02-08 22:27 ` Michael Kerrisk
2009-02-08 22:12 ` Michael Kerrisk
2009-02-09 2:24 ` Greg KH
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=cfd18e0f0902081025t3fe333ev1616af990e6d19ce@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®