[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[Libevent-users] shutdown behavior of bufferevents

To: libevent-users@xxxxxxxxxxxxx
Subject: [Libevent-users] shutdown behavior of bufferevents
From: Roman Gershman <roman@xxxxxxxxx>
Date: Fri, 21 Jun 2013 21:23:38 +0300
Delivered-to: archiver@xxxxxxxx
Delivered-to: libevent-users-outgoing@xxxxxxxx
Delivered-to: libevent-users@xxxxxxxx
Delivery-date: Fri, 21 Jun 2013 14:23:47 -0400
Reply-to: libevent-users@xxxxxxxxxxxxx
Sender: owner-libevent-users@xxxxxxxxxxxxx

Hi,

I am trying to understand the invariants the libevent library provides when we free its resources.

Specifically, if I call bufferevent_free(my_bev) in a thread different from the main event_loop thread, is it guaranteed that my_bev's callbacks will never run after bufferevent_free call completes?

Moreover, if the callbacks were running during the call to bufferevent_free(), is it guaranteed that they finished to run as well? Does BEV_OPT_UNLOCK_CALLBACKS affect this behavior?

Note that I do not use BEV_OPT_DEFER_CALLBACKS flag.

I am using 2.0.19-stable version of libevent library.

Thanks!

Follow-Ups:
- [Libevent-users] Re: shutdown behavior of bufferevents
  - From: Roman Gershman

Prev by Author: Re: [Libevent-users] select() call overflow from libevent for different OS
Next by Author: [Libevent-users] Re: shutdown behavior of bufferevents
Previous by thread: Re: [Libevent-users] Triggered EV_READ event socket get ENOT Transport endpoint is not connected
Next by thread: [Libevent-users] Re: shutdown behavior of bufferevents
Index(es):
- Author
- Thread