Topic: [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?
Do you need HAVE_THREAD_LS if you're building wolfSSL for Visual Studio? What happens if you don't use it?
You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → wolfSSL → [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?
Do you need HAVE_THREAD_LS if you're building wolfSSL for Visual Studio? What happens if you don't use it?
Hi raysatiro,
HAVE_THREAD_LS is not required for building wolfSSL for Visual Studio, but is optional. What this does is use thread local storage for the ECC fixed point cache. If HAVE_THREAD_LS is not defined, wolfSSL will instead use mutex locks around the ECC fixed point cache.
Best Regards,
Chris
That sounds like it could help with performance if multiple threads are using wolfSSL. Is there any disadvantage to enabling it in Windows?
A possible disadvantage would be slightly higher stack use per thread, since you now have an ECC fixed point cache per thread, instead of one global cache. The upside is that it may be more performant as you no longer have to lock/unlock mutexes on the cache.
wolfSSL - Embedded SSL Library → wolfSSL → [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.016 seconds (89% PHP - 11% DB) with 11 queries