On Tue, Mar 29, 2011 at 11:30 PM, Arlen Cuss wrote:
> My question now: say both the ev_timer and ev_io get triggered at the
> same time. If the ev_timer callback gets called first, then the ev_io is
> stopped and deallocated (as is all the auxiliary data that the ev_io
> callback will be using, as
Hi all,
I'm using an ev_timer to timeout an operation where an ev_io may be
either listening for reads or writes. The ev_io watcher is allocated in
a struct which - if the ev_timer is triggered - gets deallocated. The
ev_io is of course stopped before its memory disappears.
My question now: say b
Hi Marc,
> I'm using one event loop per thread, and so
> > far the best I've been able to come up with is to "round-robin" the
> > ev_io watcher on the listening socket itself [2]:
>
> (the leader/follower-pattern)
Aha.
> If you use linux and epoll, then yes, every start and stop will likely l
Hi Maarten,
You make a very good point. I suppose I was wanting to avoid having to
use mutexes (muticies? ;-)) and ev_async to be constantly stopping the
other threads to hand them work.
It seems to me that the threads *do* seem to get scheduled across the
cores (i.e. it's not a requirement that
Dear all,
I am fighting since some hours on migrating a libev C to a C++
implementation. For some unknown reasons, Visual Studio accepts a simple
function setting (ev::io iow; iow.set();), but not method settings
(iow2.set(&Cobj) ;) !! VS does the same error
code on different VS version!
I fixed
