The _POSIX_CLOCK_SELECTION option introduces the functions
pthread_condattr_getclock()
pthread_condattr_setclock()
to allow the pthread_cond_timedwait() function to use a clock other than
the default one. But the _POSIX_TIMEOUTS option introduces new variants
of the timed-wait functions for mutexes, rwlocks, semaphores, message
queues, and the POSIX trace facility. But for none of these the
_setclock/_getclock functions exist.
Shouldn't there be
pthread_mutexattr_getclock()
pthread_mutexattr_setclock()
pthread_rwlockattr_getclock()
pthread_rwlockattr_setclock()
sem_getclock()
sem_setclock()
posix_trace_attr_setclock()
posix_trace_attr_getclock()
and shouldn't the mq_attr structure contain
clockid_t mq_clock
The proposed semaphore and message functionality is perhaps not really
usable since the would modify the running object but perhaps the use can
be restricted.
The use of alternative clocks is very useful and restricting it to
conditional variables seems to be an oversight.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
signature.asc
Description: This is a digitally signed message part
|