| /external/grpc-grpc/doc/ |
| D | fork_support.md | 4 due to the GIL (global interpreter lock). Extension modules can release
5 the GIL in CPU bound tasks, but that isn't an option in pure Python.
7 etc, to work around the GIL. These modules call ```fork()``` underneath the hood. Various issues ha…
|
| /external/llvm-project/lldb/source/Plugins/ScriptInterpreter/Python/ |
| D | PythonDataObjects.cpp | 1002 class GIL { class
1004 GIL() { in GIL() function in __anon89da3f040111::GIL
1008 ~GIL() { PyGILState_Release(m_state); } in ~GIL()
1142 GIL takeGIL; in ~OwnedPythonFile()
1150 GIL takeGIL; in IsPythonSideValid()
1166 GIL takeGIL; in Close()
1258 GIL takeGIL; in Close()
1268 GIL takeGIL; in Flush()
1276 GIL takeGIL; in GetOptions()
1303 GIL takeGIL; in Write()
[all …]
|
| /external/python/pybind11/docs/advanced/ |
| D | misc.rst | 39 Global Interpreter Lock (GIL)
42 When calling a C++ function from Python, the GIL is always held.
59 /* Acquire GIL before calling Python code */
81 /* Release GIL before calling into (potentially long-running) C++ code */
201 // perform cleanup here -- this function is called with the GIL held
229 // perform cleanup here -- this function is called with the GIL held
248 // perform cleanup here -- this function is called with the GIL held
|
| D | embedding.rst | 257 2. Managing multiple threads, multiple interpreters and the GIL can be
|
| /external/python/cpython2/Doc/c-api/ |
| D | file.rst | 67 the :term:`GIL` is released it must also call the :c:func:`PyFile_IncUseCount` and
80 The :term:`GIL` must be held while calling this function.
83 you release the GIL::
103 The :term:`GIL` must be held while calling this function (see the example
|
| D | init.rst | 344 single: GIL
351 interpreter lock` or :term:`GIL`, that must be held by the current thread before
360 :term:`GIL` may operate on Python objects or call Python/C API functions.
375 Releasing the GIL from extension code
378 Most extension code manipulating the :term:`GIL` has the following simple
424 the GIL, but it can also be useful before calling long-running computations
427 standard :mod:`zlib` and :mod:`hashlib` modules release the GIL when
440 management), they don't hold the GIL, nor is there a thread state structure
446 creating a thread state data structure, then acquiring the GIL, and finally
449 the GIL, and finally free the thread state data structure.
[all …]
|
| /external/python/cpython2/Misc/ |
| D | valgrind-python.supp | 50 Suppress leaking the GIL. Happens once per process, see comment in ceval.c.
58 Suppress leaking the GIL after a fork.
76 Hmmm, is this a real leak or like the GIL?
|
| /external/python/cpython2/Doc/library/ |
| D | autogil.rst | 30 thread, that will lock and unlock the Global Interpreter Lock (GIL) at
|
| D | hashlib.rst | 131 The Python GIL is released to allow other threads to run while
193 three times slower and doesn't release the GIL.
|
| /external/python/cpython3/Tools/c-analyzer/cpython/ |
| D | README | 17 problem under subinterpreters if they are no longer sharing the GIL,
18 since the GIL protects us from a lot of race conditions. Keep in mind
|
| /external/python/cpython3/Doc/c-api/ |
| D | init.rst | 653 interpreter lock` or :term:`GIL`, that must be held by the current thread before
662 :term:`GIL` may operate on Python objects or call Python/C API functions.
677 Releasing the GIL from extension code
680 Most extension code manipulating the :term:`GIL` has the following simple
725 the GIL, but it can also be useful before calling long-running computations
728 standard :mod:`zlib` and :mod:`hashlib` modules release the GIL when
741 management), they don't hold the GIL, nor is there a thread state structure
747 creating a thread state data structure, then acquiring the GIL, and finally
750 the GIL, and finally free the thread state data structure.
847 In Python 3.6 and older, this function created the GIL if it didn't exist.
[all …]
|
| D | memory.rst | 100 functions are thread-safe, the :term:`GIL <global interpreter lock>` does not
174 The :term:`GIL <global interpreter lock>` must be held when using these
280 The :term:`GIL <global interpreter lock>` must be held when using these
431 thread-safe: the :term:`GIL <global interpreter lock>` is not held when the
453 - Check that the :term:`GIL <global interpreter lock>` is held when
472 if the GIL is held when functions of :c:data:`PYMEM_DOMAIN_OBJ` and
|
| /external/python/cpython3/Misc/ |
| D | valgrind-python.supp | 50 Suppress leaking the GIL. Happens once per process, see comment in ceval.c.
58 Suppress leaking the GIL after a fork.
76 Hmmm, is this a real leak or like the GIL?
|
| /external/python/cryptography/docs/hazmat/bindings/ |
| D | openssl.rst | 43 because it has to acquire the GIL whenever any lock operations occur within
|
| /external/grpc-grpc/src/python/grpcio/grpc/_cython/ |
| D | cygrpc.pyx | 55 # We have Python callbacks called by c-core threads, this ensures the GIL
|
| /external/python/cpython3/Misc/NEWS.d/ |
| D | 3.9.0b2.rst | 68 Fix GIL usage in :c:func:`PyOS_Readline`: lock the GIL to set an exception
485 called with the GIL released.
|
| D | 3.6.0b3.rst | 65 Fix "Python memory allocator called without holding the GIL" crash in
|
| D | 3.7.0b1.rst | 182 Py_Initialize() now creates the GIL. The GIL is no longer created "on
|
| D | 3.9.0a5.rst | 224 exits before trying to take the GIL.
1114 function name to check if a frame tries to acquire the GIL, instead of
1116 a different condition than the GIL.
|
| /external/python/cpython2/Doc/faq/ |
| D | library.rst | 357 A :term:`global interpreter lock` (GIL) is used internally to ensure that only
401 .. XXX link to dbeazley's talk about GIL?
403 The :term:`global interpreter lock` (GIL) is often seen as a hindrance to Python's
406 (almost) all Python code can only run while the GIL is held.
409 patch set (the "free threading" patches) that removed the GIL and replaced it
412 using the GIL. On Linux the performance loss was even worse because pthread
415 Since then, the idea of getting rid of the GIL has occasionally come up but
424 extension can release the GIL while the thread of execution is in the C code and
427 It has been suggested that the GIL should be a per-interpreter-state lock rather
|
| /external/python/cpython3/Doc/faq/ |
| D | library.rst | 371 A :term:`global interpreter lock` (GIL) is used internally to ensure that only one
414 .. XXX link to dbeazley's talk about GIL?
416 The :term:`global interpreter lock` (GIL) is often seen as a hindrance to Python's
419 (almost) all Python code can only run while the GIL is held.
422 patch set (the "free threading" patches) that removed the GIL and replaced it
427 necessary to compensate for the removal of the GIL.
438 perform a time-consuming task, the extension can release the GIL while the
443 It has been suggested that the GIL should be a per-interpreter-state lock rather
|
| /external/grpc-grpc/src/python/grpcio/grpc/_cython/_cygrpc/ |
| D | server.pyx.pxi | 146 # much but repeatedly release the GIL and wait
|
| /external/python/pyopenssl/doc/ |
| D | ChangeLog_old.txt | 145 * OpenSSL/crypto/pkey.c: Release the GIL around RSA and DSA key
491 whenever it is necessary to release or re-acquire the GIL.
500 global_info_callback so that they acquire the GIL before
656 it was too generous about giving away the GIL.
|
| /external/python/cpython3/Doc/library/ |
| D | hashlib.rst | 56 For better multithreading performance, the Python :term:`GIL` is released for
182 The Python GIL is released to allow other threads to run while hash
267 three times slower and doesn't release the GIL.
|
| D | devmode.rst | 48 * Unsafe usage of the GIL
|