STINNER Victor <vstin...@python.org> added the comment:

On Unix, PyCOND_TIMEDWAIT() is implemented with pthread_cond_timedwait(). If 
pthread_condattr_setclock() is available, it uses CLOCK_MONOTONIC. Otherwise, 
it uses CLOCK_REALTIME.

The glibc 2.30 adds pthread_cond_clockwait() which could be used to use 
CLOCK_MONOTONIC. But if pthread_cond_clockwait() is available (glibc 2.30 or 
newer), it expects that pthread_condattr_setclock() is also available. So I'm 
not sure that it's worth it to change PyCOND_TIMEDWAIT().

See the _PyThread_cond_after() function which computes an absolute timestamp 
(timespec) from a relative timeout in microseconds.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue41710>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to