[go-nuts] Re: thread local storage of C library from go application

2020-04-24 Thread Pavan
Thanks Tamas for elaborating. So if i understand, the C library will see the calls as if application is single threaded, i mean a single goroutine/thread issues C calls. ofcourse go library can manage to distribute to different gorotuines/threads based on the API type . will give more thoughts

[go-nuts] Re: thread local storage of C library from go application

2020-04-22 Thread Tamás Gulácsi
2020. április 22., szerda 10:04:37 UTC+2 időpontban Pavan a következőt írta: > > > Hi, > putting the lockosthread from library cant match with goroutines TLS and > its complex on handling goroutines exit and mapping all the GO api's (C > fns if any with them ) called by applications to same O

[go-nuts] Re: thread local storage of C library from go application

2020-04-22 Thread Pavan
Hi, putting the lockosthread from library cant match with goroutines TLS and its complex on handling goroutines exit and mapping all the GO api's (C fns if any with them ) called by applications to same OS thread . ofcourse applications cant call lockosthread too as they are not aware of t

[go-nuts] Re: thread local storage of C library from go application

2020-04-22 Thread Pavan
Thanks Tamas , I see earlier discussion too on this https://groups.google.com/forum/#!topic/golang-nuts/8Tdb-aCeYFY. As I understand, the GO library should lock the current go routine to thread, if it involves C functions with TLS data and unlock after completing such C functions . Regards,