From: Mike Crowe <mac@mcrowe.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "mtk.manpages@gmail.com Adhemerval Zanella"
<adhemerval.zanella@linaro.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: Problems with the new pthread clock implementations
Date: Sat, 21 Nov 2020 20:10:32 +0000 [thread overview]
Message-ID: <20201121201032.GA5620@mcrowe.com> (raw)
In-Reply-To: <877dqeo5f5.fsf@nanos.tec.linutronix.de>
Hi Thomas,
On Saturday 21 November 2020 at 20:50:38 +0100, Thomas Gleixner wrote:
> On Sat, Nov 21 2020 at 07:59, Michael Kerrisk wrote:
> > I've been taking a closer look at the the new pthread*clock*() APIs:
> > pthread_clockjoin_np()
> > pthread_cond_clockwait()
> > pthread_mutex_clocklock()
> > pthread_rwlock_clockrdlock()
> > pthread_rwlock_clockwrlock()
> > sem_clockwait()
>
> Is there any at least rudimentary specification of these functions and
> what they are supposed to do?
The short answer is that they are like their "timed" equivalents, but they
also accept a clockid. The longer answer is at
https://www.austingroupbugs.net/view.php?id=1216 and if you have access to
it
https://www.opengroup.org/austin/restricted/newapis-p1/Additional_APIs_for_Issue_8-part1-changedpages.pdf
HTH.
Mike.
prev parent reply other threads:[~2020-11-21 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 6:59 Problems with the new pthread clock implementations Michael Kerrisk (man-pages)
2020-11-21 17:54 ` Mike Crowe
2020-11-21 21:41 ` Michael Kerrisk (man-pages)
2020-11-23 14:38 ` Adhemerval Zanella
2020-11-23 16:12 ` Michael Kerrisk (man-pages)
2020-11-21 19:50 ` Thomas Gleixner
2020-11-21 20:10 ` Mike Crowe [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201121201032.GA5620@mcrowe.com \
--to=mac@mcrowe.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.