<![CDATA[wolfSSL - Embedded SSL Library — [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?]]> https://www.wolfssl.com/forums/topic782-solved-is-havethreadls-needed-for-visual-studio.html Thu, 31 Mar 2016 22:36:08 +0000 PunBB <![CDATA[Re: [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?]]> https://www.wolfssl.com/forums/post2468.html#p2468 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.

]]> Thu, 31 Mar 2016 22:36:08 +0000 https://www.wolfssl.com/forums/post2468.html#p2468 <![CDATA[Re: [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?]]> https://www.wolfssl.com/forums/post2463.html#p2463 That sounds like it could help with performance if multiple threads are using wolfSSL. Is there any disadvantage to enabling it in Windows?

]]> Fri, 25 Mar 2016 22:59:39 +0000 https://www.wolfssl.com/forums/post2463.html#p2463 <![CDATA[Re: [SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?]]> https://www.wolfssl.com/forums/post2460.html#p2460 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

]]> Fri, 25 Mar 2016 22:16:19 +0000 https://www.wolfssl.com/forums/post2460.html#p2460 <![CDATA[[SOLVED] Is HAVE_THREAD_LS needed for Visual Studio?]]> https://www.wolfssl.com/forums/post2454.html#p2454 Do you need HAVE_THREAD_LS if you're building wolfSSL for Visual Studio? What happens if you don't use it?

]]> Wed, 23 Mar 2016 22:40:12 +0000 https://www.wolfssl.com/forums/post2454.html#p2454