Dear Matt, On Thu, Oct 8, 2015 at 3:17 PM, Matt Caswell <m...@openssl.org> wrote:
> > > No. I think you are confusing two different things. > > 1) How does an *application* perform asynchronous work (via libssl or > libcrypto) using an asynchronous capable engine? > Ok. There is an example an explanation you have provided. > > 2) How does an asynchronous capable engine offload async work to its > hardware? > > These patches solve the first problem only. It provides an API and > mechanism for control to pass between the application and engine and > back again (perhaps multiple times) during the invocation of a long > running crypto operation. It also provides some mechanisms to enable an > engine to signal the completion of work to the application. > > The second problem is entirely engine dependant. It will be a different > solution for different hardware. These patches do not provide a solution > to that problem. > So I do not understand what you mean by "offload" :-( I understand that it's an engine-dependent, but I can't imagine a corresponding pseudo code. -- SY, Dmitry Belyavsky
_______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
