2017-09-08 02:51:28 -03:00
|
|
|
#ifndef Py_INTERNAL_GIL_H
|
|
|
|
#define Py_INTERNAL_GIL_H
|
|
|
|
#ifdef __cplusplus
|
|
|
|
extern "C" {
|
|
|
|
#endif
|
|
|
|
|
2019-04-17 18:02:26 -03:00
|
|
|
#ifndef Py_BUILD_CORE
|
|
|
|
# error "this header requires Py_BUILD_CORE define"
|
2018-11-09 08:03:37 -04:00
|
|
|
#endif
|
|
|
|
|
2018-10-31 20:52:28 -03:00
|
|
|
#include "pycore_condvar.h"
|
|
|
|
#include "pycore_atomic.h"
|
2018-10-30 11:14:25 -03:00
|
|
|
|
2017-09-08 02:51:28 -03:00
|
|
|
#ifndef Py_HAVE_CONDVAR
|
2018-10-30 11:14:25 -03:00
|
|
|
# error You need either a POSIX-compatible or a Windows system!
|
2017-09-08 02:51:28 -03:00
|
|
|
#endif
|
|
|
|
|
|
|
|
/* Enable if you want to force the switching of threads at least
|
|
|
|
every `interval`. */
|
|
|
|
#undef FORCE_SWITCHING
|
|
|
|
#define FORCE_SWITCHING
|
|
|
|
|
|
|
|
struct _gil_runtime_state {
|
|
|
|
/* microseconds (the Python API uses seconds, though) */
|
|
|
|
unsigned long interval;
|
|
|
|
/* Last PyThreadState holding / having held the GIL. This helps us
|
|
|
|
know whether anyone else was scheduled after we dropped the GIL. */
|
|
|
|
_Py_atomic_address last_holder;
|
|
|
|
/* Whether the GIL is already taken (-1 if uninitialized). This is
|
|
|
|
atomic because it can be read without any lock taken in ceval.c. */
|
|
|
|
_Py_atomic_int locked;
|
|
|
|
/* Number of GIL switches since the beginning. */
|
|
|
|
unsigned long switch_number;
|
|
|
|
/* This condition variable allows one or several threads to wait
|
|
|
|
until the GIL is released. In addition, the mutex also protects
|
|
|
|
the above variables. */
|
|
|
|
PyCOND_T cond;
|
|
|
|
PyMUTEX_T mutex;
|
|
|
|
#ifdef FORCE_SWITCHING
|
|
|
|
/* This condition variable helps the GIL-releasing thread wait for
|
|
|
|
a GIL-awaiting thread to be scheduled and take the GIL. */
|
|
|
|
PyCOND_T switch_cond;
|
|
|
|
PyMUTEX_T switch_mutex;
|
|
|
|
#endif
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
#endif /* !Py_INTERNAL_GIL_H */
|