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
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. Wa
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
>
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 expir
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 t
[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
http://www.kernel.org/pub/linu
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 buffe
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 fil
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 wel
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
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 -- s
11 matches
Mail list logo