Inside the Go's scheduler, what will happen when an M that already has P attached cannot find a G both from local runqueue (include trying to steal from other P's) and global runqueue.
Will the M keep trying in a busy waiting manner? If so, would this makes the CPU usage in a high level? If not, suppose the M go to idle, e.g. wait on some condition variable stuff. Then when it will get wake up? -- 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/4ad7ef1c-9ec9-4810-8f6c-035fcb534c10n%40googlegroups.com.
