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 the GO API internals of c functions usage. I think this complexity will stay if the C library is called from GO, please suggest if i missed anything. Regards, On Wednesday, April 22, 2020 at 12:29:29 PM UTC+5:30, Pavan wrote: > > 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, > > > > On Tuesday, April 21, 2020 at 11:12:50 PM UTC+5:30, Tamás Gulácsi wrote: >> >> Lock C-calling goroutines to their threads with runtime LockOSThread and >> communicate with them through channels. > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/da9e330a-20f7-4047-bf2c-8ff1f10fc284%40googlegroups.com.
