Question

This may sound like a stupid question, but if one locks a resource in a multi-threaded app, then the operation that happens on the resource, is that done atomically?

I.E.: can the processor be interrupted or can a context switch occur while that resource has a lock on it? If it does, then nothing else can access this resource until it’s scheduled back in to finish off it’s process. Sounds like an expensive operation.

Answer 1

The processor can very definitely still switch to another thread, yes. Indeed, in most modern computers there can be multiple threads running simultaneously anyway. The locking just makes sure that no other thread can acquire the same lock, so you can make sure that an operation on that resource is atomic in terms of that resource. Code using other resources can operate completely independently.

You should usually lock for short operations wherever possible. You can also choose the granularity of locks… for example, if you have two independent variables in a shared object, you could use two separate locks to protect access to those variables. That will potentially provide better concurrency – but at the same time, more locks means more complexity and more potential for deadlock. There’s always a balancing act when it comes to concurrency.