Re: timerfd waking up before timer really expires

On Wed, Mar 4, 2015 at 5:06 AM, Clemens Ladisch wrote: > Lucas De Marchi wrote: >> I was debugging my application and noticed that a timerfd event was being >> triggered *before* the timer expires. >> >> I reduced the scope of the program to test a single timerfd and measure the >> difference in

Re: timerfd waking up before timer really expires

Lucas De Marchi wrote: > I was debugging my application and noticed that a timerfd event was being > triggered *before* the timer expires. > > I reduced the scope of the program to test a single timerfd and measure the > difference in the result of clock_gettime() between two reads. > >

Re: timerfd waking up before timer really expires

On Wed, Mar 4, 2015 at 5:06 AM, Clemens Ladisch clem...@ladisch.de wrote: Lucas De Marchi wrote: I was debugging my application and noticed that a timerfd event was being triggered *before* the timer expires. I reduced the scope of the program to test a single timerfd and measure the

Re: timerfd waking up before timer really expires

Lucas De Marchi wrote: I was debugging my application and noticed that a timerfd event was being triggered *before* the timer expires. I reduced the scope of the program to test a single timerfd and measure the difference in the result of clock_gettime() between two reads. loop_time_fd

timerfd waking up before timer really expires

Hi, I was debugging my application and noticed that a timerfd event was being triggered *before* the timer expires. I'd like to know if this behavior is expected. More details below. I reduced the scope of the program to test a single timerfd and measure the difference in the result of

timerfd waking up before timer really expires

Hi, I was debugging my application and noticed that a timerfd event was being triggered *before* the timer expires. I'd like to know if this behavior is expected. More details below. I reduced the scope of the program to test a single timerfd and measure the difference in the result of