From: Clemens Ladisch <clemens@ladisch.de>
To: Johannes Lorenz <johannes89@mailueberfall.de>,
alsa-devel@alsa-project.org
Subject: Re: parallel, real time safe waiting?
Date: Tue, 14 Apr 2015 14:35:36 +0200 [thread overview]
Message-ID: <552D0998.4080806@ladisch.de> (raw)
In-Reply-To: <trinity-43de15d6-c64e-46fe-80ab-acaeb4930fc6-1428947762351@3capp-gmx-bs04>
Johannes Lorenz wrote:
> 1.) Let each thread open a handle using snd_seq_open()
> 2.) Call snd_pcm_wait() in each thread
> Are these functions
>
> a) real time safe?
snd_seq_open() is not, but why would that matter?
Don't you call it from the GUI thread?
> b) race-condition free, assuming I'll use pairwise different handles each thread
Yes.
Regards,
Clemens
next prev parent reply other threads:[~2015-04-14 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 17:56 parallel, real time safe waiting? Johannes Lorenz
2015-04-14 12:35 ` Clemens Ladisch [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-14 18:39 Johannes Lorenz
2015-04-14 19:49 ` Clemens Ladisch
2015-04-14 20:03 Johannes Lorenz
2015-04-15 7:52 ` Clemens Ladisch
2015-04-15 15:51 Johannes Lorenz
2015-04-15 19:41 ` Clemens Ladisch
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=552D0998.4080806@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=johannes89@mailueberfall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox