Re:Global Interpreter Lock, or how to kill it
by jerf on Wednesday June 29, 2011 @05:27PM
(#2711438)
Failed for CPython or failed for PyPy? I'm just going on the claim that PyPy is in a position to automatically add STM, per that blog post. If in fact it can't automatically add locks, it isn't going to be automatically adding STM either and this is all a moot discussion.
Re:Global Interpreter Lock, or how to kill it
by jholman on Wednesday June 29, 2011 @10:07PM
(#2712205)
Adding fine-grained locks without risking deadlock is pretty tricky. Perhaps too tricky for automatic addition.
As I (shallowly) understand it, STM doesn't introduce deadlock threats, so it requires less-amazing feats to add it automatically.
Note, again, that the FA does admit that using STM will perform more poorly than fine-grained locking, and he only hopes that it will scale well enough that extra cores will pay for it.
As I understand it, one of the reasons for the GIL is that it makes it easier to write C extensions (especially as compared with fine-grained locking, which is not friendly to extensions), and I'm not sure, but I think the STM scheme preserves this property?
So far thinking about how to really do that automatically failed. Do you feel like providing an idea?