➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients beazley, dabeaz, flox, kristjan.jonsson, loewis, pitrou, techtonik, torsten
Date 2010-04-13.23:22:58
SpamBayes Score 2.3893021e-08
Marked as misclassified No
Message-id <4BC4FCD1.6090408@v.loewis.de>
In-reply-to <1271198922.88.0.338644168251.issue8299@psf.upfronthosting.co.za>
Content 
> Maybe the state of this discussion is my fault for not being clear
> enough. Let's abandon terms such as "broken" and "roundrobin."  CS
> theory has the perfectly useful terms "fair" and "unfair."  The fact
> of the matter is this: the pthread GIL (implemented as LEGACY gil) is
> an "unfair" syncronization primitve.

That's not really true. The Linux condition variable (from glibc
linuxthreads), for example, implements "fair" synchronization. Other
implementations may do the same.
History
Date User Action Args
2010-04-13 23:23:00loewissetrecipients: + loewis, beazley, pitrou, kristjan.jonsson, techtonik, flox, dabeaz, torsten
2010-04-13 23:22:58loewislinkissue8299 messages
2010-04-13 23:22:58loewiscreate