Re: pthread_mutex_timedlock() vs. clock_settime()

["Joël Krähemann" <jkraehemann@gmail.com>]

Hi,

At my opinion, if you do really parallelism you should make use of
something like this:

https://www.nongnu.org/gsequencer/api/4.2.0/libags/thread.html

The AgsThread::run() function is what you usually override to run your
parallel code.

AgsConcurrencyProvider::get_task_launcher() can be used to run in
conflict free context, without any parallelism.
Your AgsTask implementation is launched while the tree is fully synchronized ...

What I want to say is, parallelism is a complex topic and libags.so
would provide abstraction to it.

regards,
Joël

On Mon, Aug 1, 2022 at 9:10 AM Joël Krähemann <jkraehemann@gmail.com> wrote:
>
> Hi Sebastian,
>
> You have a dead-lock, probably. I just looked at your code. You are
> using non-recursive mutices and I think this mutex was locked twice by
> the very same thread.
>
>  Your code is buggy.
>
> regards,
> Joël
>
> On Mon, Aug 1, 2022 at 8:47 AM Sebastian Huber
> <sebastian.huber@embedded-brains.de> wrote:
> >
> > Hello,
> >
> > I use the attached test program to check several POSIX functions which
> > use an absolute CLOCK_REALTIME timeout. I noticed that the
> > pthread_mutex_timedlock() with clock_settime() test cases doesn't work
> > (it doesn't time out when the CLOCK_REALTIME is set past the time out
> > time point). The test case works for the other synchronization objects,
> > for example semaphores (sem_timedwait()) or condition variables
> > (pthread_cond_timedwait()). I am not sure if this is a problem with my
> > understanding of the POSIX standard, my test case implementation, or the
> > glibc/Linux version. I use Linux 5.3.18.
> >
> > --
> > 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/