use ONLY dynamic locks. So, or ONLY static
locks, or both static and dynamic.
Thank you very much for your answer, Brian.
From: bebro...@rockwellcollins.com
Sent: Tuesday, May 15, 2012 5:50 PM
To: openssl-users@openssl.org
Subject: Re: Multi-threaded applications, locking_function
ml.vladimbe...@gmail.com
Sent by: owner-openssl-us...@openssl.org
05/13/2012 02:04 PM
Please respond to
openssl-users@openssl.org
To
openssl-users@openssl.org
cc
Subject
Re: Multi-threaded applications, locking_function, threadid_func, dynamic
locks
From: Dr. Stephen Henson
Sent: Sunday, May 13
On Sun, May 13, 2012, Vladimir Belov wrote:
Hello.
1) If I will use each OpenSSL object only by one thread at the
moment, it can be different thread each time but never two or more
threads will use one object simultaneously do I need to use
locking_function and threadid_func or no?
Yes
From: Dr. Stephen Henson
Sent: Sunday, May 13, 2012 5:53 PM
Yes because some structures need to be locked internally. An example is
the
error queue.
I draw a conclusion: in multi-threaded application using of
locking_function and threadid_func is mandatory. Ok.
Currently dynamical locks
Hello.
1) If I will use each OpenSSL object only by one thread at the moment, it
can be different thread each time but never two or more threads will use one
object simultaneously do I need to use locking_function and threadid_func or
no?
2) Performance of dynamic locks in comparison with
