Gordon, Just quick question for you, have you seen any dynamic mutex lock been created while your openssl application is running? I implemented both static and dynamic locking mechanism in my application. I can see that there are a total of 41 static mutex locks been created during initialization but I haven't seen any dynamic mutex lock been created and invoked by openssl functions.
Thanks Bob From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Le Huang Sent: Wednesday, March 13, 2013 8:21 PM To: openssl-users@openssl.org Subject: Re: Static and Dynamic Locking Functions Gordon, Not sure how your question relates OpenSSL, but in general, thread id is not a unique identifier for locks. On Thu, Mar 14, 2013 at 3:40 AM, Betsy Gordon <bgor...@companioncorp.com<mailto:bgor...@companioncorp.com>> wrote: Hello, I have implemented static and dynamic locking functions but have a lingering question. It is not clear to me whether the same thread would ever create more than one lock before previous locks created by that thread had been destroyed. In other words, is the thread id intended to be the unique identifier for locks? Thank you, B. Gordon ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org<mailto:openssl-users@openssl.org> Automated List Manager majord...@openssl.org<mailto:majord...@openssl.org> -- Regards, Huang Le (Eric, Alibaba DevOps) Email: 4tarhl AT gmail.com<http://gmail.com>, le.hl AT alibaba-inc.com<http://alibaba-inc.com>
