➜

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 gregory.p.smith
Recipients DazWorrall, aconrad, alex, andrix, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, jcea, jhylton, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, neologix, nirai, pitrou, rcohen, rh0dium, salgado, tarek, thouis, ysj.ray
Date 2010-04-26.05:23:23
SpamBayes Score 1.2083287e-06
Marked as misclassified No
Message-id <1272259408.32.0.32282709464.issue7946@psf.upfronthosting.co.za>
In-reply-to
Content 
Nice dabeaz.

One potential concern with "dabeaz_gil.patch 2010-04-25 21:13" is that it appears to always leave the gil_monitor thread running.  This is bad on mobile/embedded platforms where waking up at regular intervals prevents advanced sleep states and wastes power/battery.  (practical example: the OLPC project has run into this issue in other code in the past)

Could this be modified so that gil_monitor stops looping (blocks) so long as there are only IO bound Python threads running or while no python thread owns the GIL?

In that situation a multithreaded python process that has either reverted to one thread or has all threads blocked in IO would be truly idle rather than leaving the gil_monitor polling.
History
Date User Action Args
2010-04-26 05:23:29gregory.p.smithsetrecipients: + gregory.p.smith, loewis, jhylton, jcea, pitrou, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, durin42, eric.araujo, nirai, alex, andrix, konryd, brian.curtin, flox, DazWorrall, salgado, cool-RR, rh0dium, rcohen, dabeaz, mahmoudimus, aconrad, ysj.ray, neologix, thouis
2010-04-26 05:23:28gregory.p.smithsetmessageid: <1272259408.32.0.32282709464.issue7946@psf.upfronthosting.co.za>
2010-04-26 05:23:26gregory.p.smithlinkissue7946 messages
2010-04-26 05:23:24gregory.p.smithcreate