From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: timerfd(2) draft man page plus questions
Date: Tue, 17 Jul 2007 23:04:17 +0200 [thread overview]
Message-ID: <20070717210417.257740@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707171253570.26781@alien.or.mcafeemobile.com>
> > 1. timer_settime() and setitimer() both permit the caller to obtain
> > the old value of the timer when modifying an existing timer. Why
> > doesn't timerfd() provide this functionality?
>
> I don't know ;) Would it be any useful?
Well given that the two older APIs both provide this
functionality, it seems that it is desired in applications. It
is a shame that the new API doesn't have this. It could be
added (I'm inclined to say, it should be): the only problem
is that the syscall is now out in the wild, so a change at
this point would not be ABI compatible. However, it only just
got into the wild (and hasn't made it into glibc yet), so now
would be a good time to fix it, if you are agreeable, and the
kernel gatekeepers are prepared to tolerate the ABI change.
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages ,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
next prev parent reply other threads:[~2007-07-17 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 7:15 timerfd(2) draft man page plus questions Michael Kerrisk
2007-07-17 19:55 ` Davide Libenzi
2007-07-17 21:04 ` Michael Kerrisk [this message]
2007-07-17 22:06 ` Davide Libenzi
2007-07-17 22:35 ` Michael Kerrisk
-- strict thread matches above, loose matches on Subject: below --
2007-07-17 23:15 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=20070717210417.257740@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=akpm@osdl.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox