APIs that take KernelTimeout as a parameter can now query if an absolute or relative timeout was requested. If the underlying API can only use one type of timeout, the code will do a reasonable conversion. The goal is to eventually enable the possibility of using wait times that are based on monotonic clocks that are safe against system clock steps. PiperOrigin-RevId: 508541507 Change-Id: Id08bf13515f3e1bfd78d88393cde98a6fd3ef72c
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| create_thread_identity.cc | Loading commit data... | |
| create_thread_identity.h | Loading commit data... | |
| futex.h | Loading commit data... | |
| graphcycles.cc | Loading commit data... | |
| graphcycles.h | Loading commit data... | |
| graphcycles_benchmark.cc | Loading commit data... | |
| graphcycles_test.cc | Loading commit data... | |
| kernel_timeout.cc | Loading commit data... | |
| kernel_timeout.h | Loading commit data... | |
| kernel_timeout_test.cc | Loading commit data... | |
| per_thread_sem.cc | Loading commit data... | |
| per_thread_sem.h | Loading commit data... | |
| per_thread_sem_test.cc | Loading commit data... | |
| thread_pool.h | Loading commit data... | |
| waiter.cc | Loading commit data... | |
| waiter.h | Loading commit data... |