On 03/29/10 12:54 AM, Thor Lancelot Simon wrote:
On Mon, Mar 29, 2010 at 08:03:29AM +1000, Peter Waltenberg wrote:
Historically I suspect the reason there were no default callbacks is that a
sizeable proportion of OpenSSL users didn't use threading at all, and the
baggage hauling in the thread libraries imposed was significant.
I don't think that's an issue anymore - threading is the common case now.
Maybe for some people. For others, actually doing locked-bus instructions
by default would wreck OpenSSL's performance beyond compare.
I'd be interested in seeing any benchmarks of locking vs non-locking.
Even if there is a performance impact correctness needs to come first.
Please don't make locking the default.
I'm just suggesting a compile-time option. The application could always
set the locking callbacks back to NULL if it knew what it was doing.
-M
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
