[issue7946] Convoy effect with I/O bound threads and New GIL

David Beazley report at bugs.python.org
Tue Apr 27 14:44:46 CEST 2010

David Beazley <dave at dabeaz.com> added the comment:

That second access of gil_last_holder->cpu_bound is safe because that block of code is never entered unless some other thread currently holds the GIL.   If a thread holds the GIL, then gil_last_holder is guaranteed to have a valid value.


Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list