[openssl-users] Openssl async support

[Paul Yang]

Read this: https://www.openssl.org/docs/man1.1.0/crypto/ASYNC_start_job.html <https://www.openssl.org/docs/man1.1.0/crypto/ASYNC_start_job.html>

Usually async operations happen in engines when they need to talk to hardware but you can still utilize async mechanism in pure software if you have the scenario

> On Dec 18, 2018, at 18:36, ASHIQUE CK <ckashiquekvk at gmail.com> wrote:
> 
> Hi all,
> 
> I truly understand that everyone might be busy with your work and didn't found time to reply. That's okay, but incase you have accidendly forgot to reply, please accept this as a gentle reminder.
> 
> 
> 
> 
> 
> On Mon, Dec 17, 2018 at 6:11 PM ASHIQUE CK <ckashiquekvk at gmail.com <mailto:ckashiquekvk at gmail.com>> wrote:
> Hi all,
> 
> 	I have some queries regarding OpenSSL async operation.
> 
> Current setup
> -------------
> 	I have one OpenSSL dynamic engine (with RSA and AES-GCM support) and linked it with Nginx server. Multiple WGET commands on the client side.
> 
> Current issue
> -------------
>  	Since OpenSSL do_cipher call (the function in which actual AES-GCM encryption/decryption happening) comes from one client at a time which is reducing file downloading performance. So we need an asynchronous operation in OpenSSL ie. we need multiple do_cipher calls at the same time from which we should submit requests to HW without affecting the incoming requests and should wait for HW output.
> 
> Queries
> --------
>  1) Is there is any other scheme for multiple do_cipher calls at a time?. 
>  2) Any method to enable asynchronous call from OpenSSL?   
> 
> Versions
> -------------
> Openssl - 1.1.0h
> Nginx1.11.10
> Wget 1.17.1
> 
>  Kindly support me. Please inform me if any more inputs needed. Thanks in advance.
> -- 
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20181219/10b8a9e1/attachment-0001.html>