On Tue, Jun 26, 2012 at 12:00:57PM +0200, Marek ma...@octogan.net wrote:
Here is that A_cb():
mutex.lock()
while(!queue.empty()) {
data = get_data_from_hared_queue();
flow-B_notify(data);
}
mutex.unlock();
and B_notify(data) will look like:
appropriate_queue =
On Tue, Jun 26, 2012 at 12:00:57PM +0200, Marek wrote:
Now my question is if the flow-B_notify() will end only after the
iterate_cb() function returns (so the iterate_cb will be running
with mutex still locked!)? Or rather flow-B_notify() is called,
inside the B_notify the watcher is triggered
On Tue, Jun 26, 2012 at 12:52:07PM +0200, Marc Lehmann wrote:
On Tue, Jun 26, 2012 at 12:00:57PM +0200, Marek ma...@octogan.net wrote:
Here is that A_cb():
mutex.lock()
while(!queue.empty()) {
data = get_data_from_hared_queue();
flow-B_notify(data);
}
mutex.unlock();
On Tue, 2012-06-26 at 00:01 +0200, Marc Lehmann wrote:
As you can see it translates to epoll_create1(0)
As it should, no sign of it being phased out here.
Agreed - what i showed is backward compat support (typically this
is how i have seen things get phased out).
In the noise making that
