From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: rdunlap@xenotime.net, akpm@linux-foundation.org, hch@lst.de,
geoff@gclare.org.uk, tglx@linutronix.de, david@hardeman.nu,
drepper@redhat.com, subrata@linux.vnet.ibm.com, corbet@lwn.net,
linux-kernel@vger.kernel.org
Subject: Re: Man page for revised timerfd API
Date: Thu, 27 Sep 2007 12:35:31 +0200 [thread overview]
Message-ID: <20070927103531.184550@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0709261038550.25778@alien.or.mcafeemobile.com>
Davide,
A further question: what is the expected behavior in the
following scenario:
1. Create a timerfd and arm it.
2. Wait until M timer expirations have occurred
3. Modify the settings of the timer
4. Wait for N further timer expirations have occurred
5. read() from the timerfd
Does the buffer returned by the read() contain the value
N or (M+N)? In other words, should modifying the timer
settings reset the expiration count to zero?
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-09-27 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 7:12 Man page for revised timerfd API Michael Kerrisk
2007-09-26 18:06 ` Davide Libenzi
2007-09-26 21:13 ` Michael Kerrisk
2007-09-27 10:35 ` Michael Kerrisk [this message]
2007-09-27 16:45 ` Davide Libenzi
2007-10-03 6:50 ` Michael Kerrisk
2007-10-03 8:14 ` Matti Aarnio
2007-10-04 18:19 ` Michael Kerrisk
2007-09-27 8:20 ` Geoff Clare
2007-09-27 10:50 ` Michael Kerrisk
[not found] <20070927072726.50350@gmx.net>
2007-09-27 16:42 ` Davide Libenzi
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=20070927103531.184550@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@hardeman.nu \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=geoff@gclare.org.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=subrata@linux.vnet.ibm.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 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.