Hi, I'm writing a Go library to embed/extend CPython (Pygolo <https://gitlab.com/pygolo/py>). CPython uses thread local storage and therefore I need to care about pinning goroutines to OS threads accordingly.
It's pretty much clear that when the Python interpreter is embedded it can be accessed only from one goroutine and that such goroutine must be locked to an OS thread all the time. It's possible to create Python thread states and allow multiple threads to access the interpreter, therefore other goroutines - if locked to an OS thread - can access the interpreter (modulo Python GIL). It's also clear that if the Python interpreter calls back a Go function it will happen from one of the locked threads of above and therefore nothing special needs to be done on the Go side. Or not? If a thread is locked no other goroutines are allowed to run as per documentation of LockOSThread, so on which goroutine the Go callback will actually run? Different story is when Go is used to extend the Python interpreter, when Go calls are happening in a thread not owned by the Go runtime. Here I have some doubts, I think I read something about cgo locking threads of Go callbacks but I can't find it any more. I guess that at the first Go call cgo initializes the Go runtime and suddenly a few threads and goroutines spawn to life but how the goroutine scheduling works when C is in control of the calling threads? Is it possible that multiple goroutines get scheduled on the caller C thread? Are Go callbacks goroutines reused? If not and I leave a Go callback goroutine locked to a thread, is the calling C thread going to be killed, as per documentation of LockOSThread? Thanks in advance for any clarification. Regards, Dom -- rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05 -- 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/bf3ca959-f772-4940-a48b-f21993394e2dn%40googlegroups.com.
