From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: "Joël Krähemann" <jkraehemann@gmail.com>
Cc: libc-help@sourceware.org
Subject: Re: pthread_mutex_timedlock() vs. clock_settime()
Date: Mon, 1 Aug 2022 18:31:54 +0200 [thread overview]
Message-ID: <d1cafab4-733c-0d96-85b4-70dd0f89d538@embedded-brains.de> (raw)
In-Reply-To: <CA+Owze4RD+-07yB-y6yDZTekmL+_G=RPuXrL2iJNdf1Vg2Pjag@mail.gmail.com>
Hello Joël,
this is just a test case and not a real application. There is only a
main thread and a worker thread. The worker thread should just block on
an synchronization object and then wait for a time out (or it is
cancelled). The main thread uses a simple sleep(1) to hopefully ensure
that the worker task had enough time to block on the synchronization
object under test. There are different action and done events. Since a
mutex is used, there is no need for atomic objects.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2022-08-01 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 8:43 Sebastian Huber
2022-08-01 7:10 ` Joël Krähemann
2022-08-01 7:41 ` Joël Krähemann
2022-08-03 23:44 ` Sebastian Huber
2022-08-01 8:28 ` Joël Krähemann
2022-08-01 8:36 ` Sebastian Huber
2022-08-01 9:51 ` Joël Krähemann
2022-08-01 11:51 ` Joël Krähemann
2022-08-01 11:59 ` Joël Krähemann
2022-08-01 14:44 ` Joël Krähemann
2022-08-01 16:31 ` Sebastian Huber [this message]
2022-08-01 20:11 ` Joël Krähemann
2022-08-01 22:05 ` Joël Krähemann
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=d1cafab4-733c-0d96-85b4-70dd0f89d538@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=jkraehemann@gmail.com \
--cc=libc-help@sourceware.org \
/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).