You may already know this, just in case: Forget about the mutex "locking" anything but itself. A use of the mutex doesn't actually "protect" anything else. Your code uses it as a traffic light -- so it knows when it's safe to proceed without colliding with another processes's use of some data.
Any number of goroutines can get a read lock at the same time. Only one goroutine can get a write lock at a time. If a goroutine has the write lock, no goroutine can get a read lock. Otherwise it may try to read what is in the middle of being written, which could cause unpredictable behavior. So, if you have millions of goroutines getting read locks, and a single goroutine gets a write lock, then all of the goroutines trying to get a read lock are going to block until the write lock is released. -- 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. For more options, visit https://groups.google.com/d/optout.
