Re: _st_epoll_dispatch firing too often

CN <[email protected]> Tue, 4 Dec 2012 15:33:54 -0800 (PST)
Newsgroups gmane.comp.lib.state-threads.user
Message-ID <[email protected]>
This was on two different Linux boxes, one 2.6.25.11-97.fc9.x86_64, and ano=
ther 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 pa=
tience to sit there and test which kernels don't play well.


----- Original Message -----
From: Michael Abbott <[email protected]>
To: CN <[email protected]>
Cc: "[email protected]" <state-threads-users@lists.=
sourceforge.net>
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?=A0 Your test program works fine for me on Linux and OS X:

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

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

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


---------------------------------------------------------------------------=
---
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d