From: Yann Droneaud <ydroneaud@opteya.com>
To: Mike Crowe <mac@mcrowe.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 0/7] Implement proposed POSIX _clockwait variants of existing _timedwait functions
Date: Fri, 15 Mar 2019 14:25:43 +0100 [thread overview]
Message-ID: <09a5e660c110a96dfcf0ce3327dcfc9233b83a9b.camel@opteya.com> (raw)
In-Reply-To: <cover.b0c66849a87ca79889a49f2f1f2563b1a8a15d8b.1551291557.git-series.mac@mcrowe.com>
Hi,
Le mercredi 27 février 2019 à 18:23 +0000, Mike Crowe a écrit :
> My attempts[1] to add a variant of pthread_cond_timedwait that would accept
> a clockid_t parameter led me to propose[2] to The Austin Group the addition
> of an entire family of functions that accept a clockid_t parameter to
> indicate the clock that the timespec absolute timeout parameter should be
> measured against. They responded positively to the request but an
> implementation is required before the proposal can proceed.
>
> This patch series is the first part of that implementation in glibc, it
> contains four new functions:
>
> int pthread_cond_clockwait(pthread_cond_t *cond, pthread_mutex_t *mutex,
> clockid_t clock, const struct timespec *abstime)
>
> int pthread_rwlock_clockrdlock(pthread_rwlock_t *rwlock, clockid_t clock,
> const struct timespec *abstime)
>
> int pthread_rwlock_clockwrlock(pthread_rwlock_t *rwlock, clockid_t clock,
> const struct timespec *abstime)
>
> int sem_clockwait(sem_t *restrict, clockid_t clock_id, const struct
> timespec *restrict)
>
There's also a pthread_timedjoin_np() that could benefit from having
"pthread_clockjoin_np()" sibling.
Regards.
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2019-03-15 13:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 18:23 [PATCH 0/7] Implement proposed POSIX _clockwait variants of existing _timedwait functions Mike Crowe
2019-02-27 18:23 ` [PATCH 1/7] nptl: Add clockid parameter to futex timed wait calls Mike Crowe
2019-03-05 12:39 ` Adhemerval Zanella
2019-03-10 8:59 ` Mike Crowe
2019-03-11 11:50 ` Adhemerval Zanella
2019-02-27 18:23 ` [PATCH 2/7] nptl: Add POSIX-proposed sem_clockwait Mike Crowe
2019-02-27 18:35 ` Joseph Myers
2019-03-05 13:31 ` Adhemerval Zanella
2019-03-10 16:17 ` Mike Crowe
2019-03-19 17:07 ` Adhemerval Zanella
2019-03-14 14:09 ` Yann Droneaud
2019-03-14 14:39 ` Mike Crowe
2019-02-27 18:23 ` [PATCH 3/7] nptl: Add POSIX-proposed pthread_cond_clockwait Mike Crowe
2019-03-05 16:45 ` Adhemerval Zanella
2019-05-04 20:22 ` Mike Crowe
2019-02-27 18:23 ` [PATCH 4/7] nptl: pthread_rwlock: Move timeout validation into _full functions Mike Crowe
2019-03-05 16:48 ` Adhemerval Zanella
2019-02-27 18:23 ` [PATCH 5/7] nptl/tst-rwlock14: Test pthread/rwlock_timedwrlock correctly Mike Crowe
2019-03-05 17:36 ` Adhemerval Zanella
2019-02-27 18:23 ` [PATCH 6/7] nptl/tst-rwlock: Use clock_gettime/timespec rather than gettimeofday/timeval Mike Crowe
2019-03-05 18:02 ` Adhemerval Zanella
2019-03-20 21:34 ` Mike Crowe
2019-03-14 14:44 ` Yann Droneaud
2019-02-27 18:23 ` [PATCH 7/7] nptl: Add POSIX-proposed pthread_rwlock_clockrdlock & pthread_rwlock_clockwrlock Mike Crowe
2019-03-07 12:59 ` Adhemerval Zanella
2019-03-05 12:35 ` [PATCH 0/7] Implement proposed POSIX _clockwait variants of existing _timedwait functions Adhemerval Zanella
2019-03-06 21:15 ` Joseph Myers
2019-03-10 9:12 ` Mike Crowe
2019-03-11 23:13 ` Joseph Myers
2019-03-13 21:42 ` Mike Crowe
2019-03-14 11:30 ` Adhemerval Zanella
2019-03-15 13:25 ` Yann Droneaud [this message]
2019-03-15 13:36 ` Mike Crowe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09a5e660c110a96dfcf0ce3327dcfc9233b83a9b.camel@opteya.com \
--to=ydroneaud@opteya.com \
--cc=libc-alpha@sourceware.org \
--cc=mac@mcrowe.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).