[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0709270944300.763@alien.or.mcafeemobile.com>
Date: Thu, 27 Sep 2007 09:45:34 -0700 (PDT)
From: Davide Libenzi <davidel@...ilserver.org>
To: Michael Kerrisk <mtk-manpages@....net>
cc: rdunlap@...otime.net, Andrew Morton <akpm@...ux-foundation.org>,
hch@....de, geoff@...are.org.uk, tglx@...utronix.de,
david@...deman.nu, Ulrich Drepper <drepper@...hat.com>,
subrata@...ux.vnet.ibm.com, corbet@....net,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Man page for revised timerfd API
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 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?
Every timerfd_settime() zeroes the tick counter. So in your scenario it'll
return N.
- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists