sync: eliminate global Mutex in Pool operations #24479
I'm guessing that comment refers to
It strikes me as odd that
For example, we could add newly-allocated pools to a per-G list, and move that list to the global list only when the thread running that G acquires the scheduler lock.
If we happen to miss a new
That could make
The text was updated successfully, but these errors were encountered: