On 2013-07-22 at 10:32 +0000, Miek Gieben wrote: > In this case I'm talking about using libunbound in Go and the locking issues > that can occur with wrt to the crypto library that is used. > > In Go you do not have control over the amount of OS threads the runtime uses. > Go uses goroutines and N of those routines are mapped to an OS thread at any > moment > in time.
For this sort of scenario, you want Go's runtime.LockOSThread(). -Phil _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
