[Python-Dev] Removing the GIL (Me, not you!)

Greg Ewing greg.ewing at canterbury.ac.nz
Fri Sep 14 05:43:57 CEST 2007

Prateek Sureka wrote:
> Naturally, we need to make the locking more  
> fine-grained to resolve this. Hopefully we can do so in a way that  
> does not increase the lock overhead (hence my suggestion for a lock  
> free approach using an asynch queue and a core as dedicated server).

What you don't seem to see is that this would have
no less overhead, and probably a lot *more*, than
a mutex or other standard synchronisation mechanism.
Certainly a lot more than an atomic instruction for
the incref/decref.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | Carpe post meridiem!          	  |
Christchurch, New Zealand	   | (I'm not a morning person.)          |
greg.ewing at canterbury.ac.nz	   +--------------------------------------+

More information about the Python-Dev mailing list