Author: Armin Rigo <ar...@tunes.org> Branch: extradoc Changeset: r5139:7cd30b055ba3 Date: 2014-01-23 17:56 +0100 http://bitbucket.org/pypy/extradoc/changeset/7cd30b055ba3/
Log: Updates, thanks fijal diff --git a/talk/fosdem2014/pypy-stm.pdf b/talk/fosdem2014/pypy-stm.pdf index f3bd0385c3b25dad655b28e8e9351c9255abcc72..7eeb751506bd76c8928b1bcdf200a385875f286c GIT binary patch [cut] diff --git a/talk/fosdem2014/pypy-stm.rst b/talk/fosdem2014/pypy-stm.rst --- a/talk/fosdem2014/pypy-stm.rst +++ b/talk/fosdem2014/pypy-stm.rst @@ -158,7 +158,7 @@ Summary (optimistic) ==================== -* If you are a Twisted developer... +* If you are using Twisted... * Just wait and your program will run on multiple cores ``:-)`` @@ -170,8 +170,10 @@ out of the box * ...Because of "conflicts": each event should be "often" independent, - but may not be (e.g. because they each incrementing a global counter - or similar) + but may not be + +* Example: incrementing a global counter, or otherwise changing some + global object systematically Some work left for you to do @@ -184,6 +186,17 @@ * Then you need (hopefully small) rewrites to avoid them +Some work left for us to do, first +================================== + +* Additional conflicts come from Twisted itself + +* Example: the logging system, which may need to use queues + +* This means that some of the core Python data structures (dicts, + queues...) may need refactorings too + + What is the point? ================== _______________________________________________ pypy-commit mailing list pypy-commit@python.org https://mail.python.org/mailman/listinfo/pypy-commit
