Re: Man page for revised timerfd API

2007-10-04 Thread Michael Kerrisk
Matti, Matti Aarnio wrote: > On Wed, Oct 03, 2007 at 08:50:09AM +0200, Michael Kerrisk wrote: >> Davide Libenzi wrote: >>> On Thu, 27 Sep 2007, Michael Kerrisk wrote: >>> Davide, A further question: what is the expected behavior in the following scenario: 1. Create a

Re: Man page for revised timerfd API

2007-10-04 Thread Michael Kerrisk
Matti, Matti Aarnio wrote: On Wed, Oct 03, 2007 at 08:50:09AM +0200, Michael Kerrisk wrote: Davide Libenzi wrote: On Thu, 27 Sep 2007, Michael Kerrisk wrote: Davide, A further question: what is the expected behavior in the following scenario: 1. Create a timerfd and arm it. 2. Wait

Re: Man page for revised timerfd API

2007-10-03 Thread Matti Aarnio
On Wed, Oct 03, 2007 at 08:50:09AM +0200, Michael Kerrisk wrote: > Davide Libenzi wrote: > > On Thu, 27 Sep 2007, Michael Kerrisk wrote: > > > >> Davide, > >> > >> A further question: what is the expected behavior in the > >> following scenario: > >> > >> 1. Create a timerfd and arm it. > >> 2.

Re: Man page for revised timerfd API

2007-10-03 Thread Michael Kerrisk
Davide Libenzi wrote: > On Thu, 27 Sep 2007, Michael Kerrisk wrote: > >> 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

Re: Man page for revised timerfd API

2007-10-03 Thread Michael Kerrisk
Davide Libenzi wrote: On Thu, 27 Sep 2007, Michael Kerrisk wrote: 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

Re: Man page for revised timerfd API

2007-10-03 Thread Matti Aarnio
On Wed, Oct 03, 2007 at 08:50:09AM +0200, Michael Kerrisk wrote: Davide Libenzi wrote: On Thu, 27 Sep 2007, Michael Kerrisk wrote: 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

Re: Man page for revised timerfd API

2007-09-27 Thread Davide Libenzi
On Thu, 27 Sep 2007, Michael Kerrisk wrote: > 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

Re: Man page for revised timerfd API

2007-09-27 Thread Davide Libenzi
On Thu, 27 Sep 2007, Michael Kerrisk wrote: > Hi Davide, > > A follow up to the man page text. Does passing a timerfd file > descriptor via a Unix domain socket to another process do the > expected thing? That is, the receiving process will be able to > read from the file descriptor in order

Re: Man page for revised timerfd API

2007-09-27 Thread Michael Kerrisk
[various useful comments snipped] Thanks Geoff -- I will incorporate all of the points you mentioned. 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

Re: Man page for revised timerfd API

2007-09-27 Thread Michael Kerrisk
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

Re: Man page for revised timerfd API

2007-09-27 Thread Geoff Clare
Michael Kerrisk <[EMAIL PROTECTED]> wrote, on 26 Sep 2007: > > .TH TIMERFD_CREATE 2 2007-09-26 Linux "Linux Programmer's Manual" > .SH NAME > timerfd_create, timerfd_settime, timer_gettime \- s/timer_/timerfd_/ > timers that notify via file descriptors > .SH SYNOPSIS > .\" FIXME . This header

Re: Man page for revised timerfd API

2007-09-27 Thread Geoff Clare
Michael Kerrisk [EMAIL PROTECTED] wrote, on 26 Sep 2007: .TH TIMERFD_CREATE 2 2007-09-26 Linux Linux Programmer's Manual .SH NAME timerfd_create, timerfd_settime, timer_gettime \- s/timer_/timerfd_/ timers that notify via file descriptors .SH SYNOPSIS .\ FIXME . This header file may well

Re: Man page for revised timerfd API

2007-09-27 Thread Michael Kerrisk
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

Re: Man page for revised timerfd API

2007-09-27 Thread Michael Kerrisk
[various useful comments snipped] Thanks Geoff -- I will incorporate all of the points you mentioned. 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

Re: Man page for revised timerfd API

2007-09-27 Thread Davide Libenzi
On Thu, 27 Sep 2007, Michael Kerrisk wrote: Hi Davide, A follow up to the man page text. Does passing a timerfd file descriptor via a Unix domain socket to another process do the expected thing? That is, the receiving process will be able to read from the file descriptor in order to

Re: Man page for revised timerfd API

2007-09-27 Thread Davide Libenzi
On Thu, 27 Sep 2007, Michael Kerrisk wrote: 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

Re: Man page for revised timerfd API

2007-09-26 Thread Michael Kerrisk
Hi Davide, > On Wed, 26 Sep 2007, Michael Kerrisk wrote: > > > .TH TIMERFD_CREATE 2 2007-09-26 Linux "Linux Programmer's Manual" > > .SH NAME > > timerfd_create, timerfd_settime, timer_gettime \- > > timers that notify via file descriptors > > .SH SYNOPSIS > > .\" FIXME . This header file may

Re: Man page for revised timerfd API

2007-09-26 Thread Davide Libenzi
Michael, SCB ... On Wed, 26 Sep 2007, Michael Kerrisk wrote: > .TH TIMERFD_CREATE 2 2007-09-26 Linux "Linux Programmer's Manual" > .SH NAME > timerfd_create, timerfd_settime, timer_gettime \- > timers that notify via file descriptors > .SH SYNOPSIS > .\" FIXME . This header file may well

Man page for revised timerfd API

2007-09-26 Thread Michael Kerrisk
Hi Davide, I've written a man page for the revised timerfd API. Could you review the text to make sure it matches matches the design you've intended to implement and let me know if there are any things that should be fixed or added. There are a few specific points that I'd like you to check

Man page for revised timerfd API

2007-09-26 Thread Michael Kerrisk
Hi Davide, I've written a man page for the revised timerfd API. Could you review the text to make sure it matches matches the design you've intended to implement and let me know if there are any things that should be fixed or added. There are a few specific points that I'd like you to check

Re: Man page for revised timerfd API

2007-09-26 Thread Davide Libenzi
Michael, SCB ... On Wed, 26 Sep 2007, Michael Kerrisk wrote: .TH TIMERFD_CREATE 2 2007-09-26 Linux Linux Programmer's Manual .SH NAME timerfd_create, timerfd_settime, timer_gettime \- timers that notify via file descriptors .SH SYNOPSIS .\ FIXME . This header file may well change .\

Re: Man page for revised timerfd API

2007-09-26 Thread Michael Kerrisk
Hi Davide, On Wed, 26 Sep 2007, Michael Kerrisk wrote: .TH TIMERFD_CREATE 2 2007-09-26 Linux Linux Programmer's Manual .SH NAME timerfd_create, timerfd_settime, timer_gettime \- timers that notify via file descriptors .SH SYNOPSIS .\ FIXME . This header file may well change .\