From: Tadeus Prastowo <0x66726565@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-help@sourceware.org
Subject: Re: SCHED_FIFO and pthread_cond_broadcast
Date: Fri, 17 Jan 2020 16:32:00 -0000 [thread overview]
Message-ID: <CAA1YtmvVCCe6Nhh0H00gfUibp-UQAoyxb8H-Phab4npei3Db_w@mail.gmail.com> (raw)
In-Reply-To: <ed16b2ec-5e47-8535-3060-54f7ebf1ced1@linaro.org>
Hello,
On Fri, Jan 17, 2020 at 4:09 PM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
> It is a known issues and it is being tracked at BZ#11588 [1].
Thank you very much for your information.
> Currently
> condition variable does not have PI awareness (such as userland wait
> queues) and issues default futex wait/wake calls that do not take in
> consideration the waiters priority.
>
> There were an interesting discussion about how to make condition variables
> PI enabled [2], and currently there is no easy way to fulfil both POSIX
> requirements and PI expectation with current kernel futex primitives.
>
> Last Linux Plumbers Darren Hart presented an alternative conditional
> variable implementation [3] that enables PI awareness, but it has its
> own drawbacks (it has different semantic than POSIX conditional variable
> at API level and afaik it is subject the very issue the new glibc
> conditional variable implementation solved, discussed at [4]).
>
> If your usage does not require all the POSIX specification about partial
> ordering regarding signaling, you might consider use librtpi (your example
> seems to show the expected output adapating to use it).
>
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=11588
> [2] https://www.youtube.com/watch?v=D1hGc8qJCcQ&list=UL-cj2JDu_Ac4&index=1208
> [3] https://github.com/dvhart/librtpi
> [4] https://www.austingroupbugs.net/view.php?id=609
Thank you very much for your pointers.
Once again, thank you very much for your information. I reallly appreciate it.
--
Best regards,
Tadeus
prev parent reply other threads:[~2020-01-17 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 23:00 Tadeus Prastowo
2020-01-17 15:09 ` Adhemerval Zanella
2020-01-17 16:32 ` Tadeus Prastowo [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=CAA1YtmvVCCe6Nhh0H00gfUibp-UQAoyxb8H-Phab4npei3Db_w@mail.gmail.com \
--to=0x66726565@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--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).