Matt, I have looked through the APIs. Will have to experiment with them somewhen later to see how well they will perform, but from theoretical point of view I am a bit scared of having 2 fds (and one ucontext) for every job in a pool. It seems like this could be a bit of burden in event-loop based model. For example, it is not hard to imagine a situation in node.js application with 10000 handshakes that are trying to complete in parallel. Is there any need in creating this fds unconditionally?
However, again, this is only a hypothetical situation, I'm yet to see how well it will behave in real situations. Just sharing some immediate concerns with you. Thank you, Fedor. On Thu, Feb 4, 2016 at 4:56 AM, Fedor Indutny via RT <r...@openssl.org> wrote: > Thank you very much, Matt, Rich. > > I will read through these docs tomorrow. > > On Thu, Feb 4, 2016 at 4:29 AM, Matt Caswell via RT <r...@openssl.org> > wrote: > > > > > > > On 04/02/16 06:34, Salz, Rich via RT wrote: > > > It’s late and my response was incomplete. > > > The other part has already landed in master, and that's the "async > > engine" support. > > > > See: > > > > https://www.openssl.org/docs/manmaster/crypto/ASYNC_start_job.html > > https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_mode.html (i.e. > > the SSL_MODE_ASYNC bit) > > https://www.openssl.org/docs/manmaster/ssl/SSL_waiting_for_async.html > > > > I'm working on a patch that may make some tweaks to this API, but you > > should get the idea. > > > > Matt > > > > > > > > _______________________________________________ > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev > -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3528 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev