Re: [ST-users] _st_epoll_dispatch firing too often

[CN <cu...@ya...>]

This was on two different Linux boxes, one 2.6.25.11-97.fc9.x86_64, and another 2.6.35.14-96.fc14.i686.  No VMs.
I've just tried on another box running 3.2.6-3.fc16.x86_64, and that seems to work correctly just like yours.
Perhaps it's just specific Linux kernels. I don't think anyone's got the patience to sit there and test which kernels don't play well.


----- Original Message -----
From: Michael Abbott <ya...@ya...>
To: CN <cu...@ya...>
Cc: "sta...@li..." <sta...@li...>
Sent: Wednesday, 5 December 2012 5:11 AM
Subject: Re: [ST-users] _st_epoll_dispatch firing too often

> _st_epoll_dispatch seems to fire too often when the sleepq is not empty.

On what OS?  Your test program works fine for me on Linux and OS X:

1354644462832661 MAIN diff = 1002671
1354644463832701 MAIN diff = 999990
1354644464832747 MAIN diff = 1000027
1354644465832793 MAIN diff = 1000026
1354644466832836 MAIN diff = 1000020

(I made it print the current st_utime() instead of the pointers, in the first column.)
The "ST diff" messages never even appear.

Are you running in a virtual machine?  VMs have been known to fire timers at unexpected times.