Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread counterpoint
Thanks, very helpful. We only support 64 bit. -- View this message in context: http://openssl.6102.n7.nabble.com/Find-size-of-available-data-prior-to-ssl-read-tp61722p61746.html Sent from the OpenSSL - User mailing list archive at Nabble.com. ___ open

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf > Of counterpoint > Sent: Thursday, December 17, 2015 11:35 > > Thanks, that makes sense. My ability to optimise is constrained - the system > is a product so I do not know what the actual pattern of usage will be. But > th

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread counterpoint
Thanks, that makes sense. My ability to optimise is constrained - the system is a product so I do not know what the actual pattern of usage will be. But there is a limit on buffer size within the system. It's a defined symbol, so can be altered from the default of 32 KB, but only by recompiling the

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf > Of counterpoint > Sent: Thursday, December 17, 2015 04:51 > > Although maybe the simple answer is to read into a temporary 32 KB buffer and > then malloc and copy. That, more or less, was my recommendation in my previous

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread Jakob Bohm
On 17/12/2015 10:36, counterpoint wrote: Thanks to Michael and Kurt for explanatory comments. Is there an available setting that gives the upper limit on the amount of data that will be obtained by a single ssl_read()? The data stream is SQL requests, and often these are quite small, but they c

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread counterpoint
Although maybe the simple answer is to read into a temporary 32 KB buffer and then malloc and copy. -- View this message in context: http://openssl.6102.n7.nabble.com/Find-size-of-available-data-prior-to-ssl-read-tp61722p61734.html Sent from the OpenSSL - User mailing list archive at Nabble.com

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-17 Thread counterpoint
Thanks to Michael and Kurt for explanatory comments. Is there an available setting that gives the upper limit on the amount of data that will be obtained by a single ssl_read()? The data stream is SQL requests, and often these are quite small, but they can run to megabytes. I need to malloc a buf

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-16 Thread Kurt Roeckx
On Wed, Dec 16, 2015 at 06:23:25PM +, Martin Brampton wrote: > Is there a way to obtain the amount of data available to be read? > > I'm working with a system that operates in non-blocking mode using epoll. > When an EPOLLIN event is received the aim is to read the data. For the > non-SSL case

Re: [openssl-users] Find size of available data prior to ssl_read

2015-12-16 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf > Of Martin Brampton > Sent: Wednesday, December 16, 2015 13:23 > > Is there a way to obtain the amount of data available to be read? > > I'm working with a system that operates in non-blocking mode using > epoll. When an