Re: [Libevent-users] Re: Avoid potential SSL read spinlocks

2011-11-16 Thread Catalin Patulea
On Wed, Nov 16, 2011 at 11:52 AM, Catalin Patulea wrote: > - Peer sends two (small) SSL records in a row (perhaps in the same TCP > segment) > - fd becomes readable, libevent delivers read_cb to bev_ssl > - bev_ssl calls SSL_read only once - does this read process only the > first record or both?

Re: [Libevent-users] Re: Avoid potential SSL read spinlocks

2011-11-16 Thread Catalin Patulea
A few things I forgot to mention: Re: bev_ssl needing deferred or not, without OPT_DEFER_CALLBACKS, https-client does not work for me. I haven't investigated. Re: SSL_read loops. Consider the following scenario: - Peer sends two (small) SSL records in a row (perhaps in the same TCP segment) - fd

Re: [Libevent-users] Re: Avoid potential SSL read spinlocks

2011-11-16 Thread Catalin Patulea
On Tue, Nov 15, 2011 at 10:25 AM, Mark Ellzey wrote: > Also, would be nice to have some code that reproduces the issue you are > having. Ok, try the attached patch against 9ae6e595 (just before your fixes). The use of an IP in the URL is incidental because of IPv6 issues on my system - you can pro