>> ... "synthetic" implementation, which would turn to kernel >> only when it actually pays off to do so and rely on user-land >> software implementation otherwise. > > Just to make sure I understand what you are saying. > > Would this implementation do something like applying some rules to > the requested operation, based on the parameters passed, and then > decide whether to use the S&ST HW, or the OpenSSL SW function?
Yes. > For > the performance reasons you listed, I have been thinking about doing > something along those lines. Good. > Is there an good reference example for this type of implementation? Unfortunately no. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
