On Sat, Oct 19, 2013 at 06:52:48PM +, "Srini Gurusu (sgurusu)"
wrote:
> >watcher is the relatively costly memory synchronisation done by
> >ev_async_send.
>
> For simplicity, if I use ev_sync_send(),
> Do we need to protect ev_sync_send() as this will be called by producer
> and
> consumer
On 10/19/13 9:09 AM, "Marc Lehmann" wrote:
>On Fri, Oct 18, 2013 at 01:49:09PM +, "Srini Gurusu (sgurusu)"
> wrote:
>> I am using async watchers ( one per each queue with priority associated
>>).
>> Can I call ev_async_send() within the async watcher callback context to
>>defer(resend withi
On Fri, Oct 18, 2013 at 01:49:09PM +, "Srini Gurusu (sgurusu)"
wrote:
> I am using async watchers ( one per each queue with priority associated ).
> Can I call ev_async_send() within the async watcher callback context to
> defer(resend within consumer context on behalf of producer) the remai
Hi libev experts,
I am migrating my application from singled threaded non locking, event-lib,
which is used in isc/bind to libev.
My application modeled in multi-threaded with n-producers and one consumer,
each thread has its own core (totally n+1 cores).
Each producer sends data over private
