Author: Antonio Cuni <[email protected]> Branch: extradoc Changeset: r5825:103974b87e0f Date: 2017-08-04 11:57 +0200 http://bitbucket.org/pypy/extradoc/changeset/103974b87e0f/
Log: some reviews diff --git a/blog/draft/remove-gil.rst b/blog/draft/remove-gil.rst --- a/blog/draft/remove-gil.rst +++ b/blog/draft/remove-gil.rst @@ -3,26 +3,30 @@ Hello everyone. -The topic of the infamous Global Interpreter Lock has been around for a while -in the Python community. There has been various attempts at removing it -(some successful ones, e.g. in Jython or IronPython with the help of the platform) -and some yet to bear fruit, like `gilectomy`_. Since February sprint in Leysin, +Discussions about the infamous Global Interpreter Lock have been around for a while +in the Python community. There has been various attempts at removing it: +some were successful, like e.g. in Jython or IronPython with the help of the platform, and some yet to bear fruit, like `gilectomy`_. Since our `February sprint`_ in Leysin, we've been on-and-off tackling the topic of GIL removal in the PyPy project. -As of Europython announcement, we're able to run (very simple) programs with GIL-less -PyPy that parallelizes nicely. The remaining 90% (and another 90%) of work -is with putting locks in strategic places so PyPy does not segfault -when you try to do a concurrent access to a data structure. +.. _`February sprint`: https://morepypy.blogspot.it/2017/03/leysin-winter-sprint-summary.html -Since such work would complicate the code base and our day to day work, -we would like to judge the interest on the community and the commercial -PyPy users. +As we announced at EuroPython, what we have got so far is a GIL-less PyPy +which can to run **very simple** multi-threaded programs which are nicely +parallelized. At the moment, non-simple programs most likely segfaults: the +remaining 90% (and another 90%) of work is with putting locks in strategic +places so PyPy does not segfault when you try to do a concurrent access to a +data structure. -We would like to do it in a following way. We are looking for a contract -with companies (individual donations did not work very well for us in the -past). We put the total cost of doing the work at $50k, out of which we -already have backing for about 1/3. If we can get a $100k contract, we would -make it our priority to deliver before the end of the year. +.. antocuni: I'd simply remove the following paragraph. It's redundant, IMHO +.. + Since such work would complicate the code base and our day to day work, + we would like to judge the interest on the community and the commercial + PyPy users. + +We are looking for commercial partners to make it happen (individual donations +did not work very well for us in the past). We estimate a total cost of $50k, +out of which we already have backing for about 1/3. If we can get a $100k +contract, we would make it our priority to deliver before the end of the year. People asked several questions, so I'll try to answer the technical parts here. _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
