Look at this well known image taken from morsmachine.dk/go-scheduler
The gray lists are local runqueues of P. If this queue get empty they will be filled with go routines from the global runqueue.
The Question is, who fills the local runqueue of P?
Scheduler, without synchronisation or every P do it for himself (mutex)?
P.S. The article omits this information.
分享All of this is taken from src/runtime/proc1.go:
Function schedule (the scheduler) calls findrunnable which attempts to steal a G from another P. If that fails, it'll return a G from the global run queue. That G is then executed on the "current" M.
In addition, schedule checks the global run queue occasionally "for fairness":
// Check the global runnable queue once in a while to ensure fairness.
// Otherwise two goroutines can completely occupy the local runqueue
// by constantly respawning each other.
In all of that, only one lock is involved, which is lock(&sched.lock).
分享
