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

[Greg Ewing]

skip at pobox.com wrote:
> what if ... we use atomic test-and-set to
> handle reference counting (with a lock for those CPU architectures where we
> haven't written the necessary assembler fragment), then implement a lock for
> each mutable type and another for global state (thread state, interpreter
> state, etc)?

Could be worth a try. A first step might be to just implement
the atomic refcounting, and run that single-threaded to see
if it has terribly bad effects on performance.

-- 
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	   +--------------------------------------+