From: Clemens Ladisch <clemens@ladisch.de>
To: "Joël Krähemann" <weedlight@gmail.com>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Atomic operations not multi-thread aware
Date: Mon, 30 Mar 2015 09:27:34 +0200 [thread overview]
Message-ID: <5518FAE6.1010308@ladisch.de> (raw)
In-Reply-To: <CANr2zYgqJ=fV9E6Dtbkw9Lhv_5r5GwuZSN0_-VT+RuLJ3ozQ4w@mail.gmail.com>
Joël Krähemann wrote:
> I can crash my application while modifying values of the LADSPA plugin
> assigned dial widget what uses atomic operations and a task engine ...
Atomic operations are thread-safe by definition.
However, plugin functions might not be. The LADSPA spec does not say
anything about it, so I guess you have to serialize all accesses.
And what does this have to do with ALSA?
Regards,
Clemens
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2015-03-30 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 14:52 Atomic operations not multi-thread aware Joël Krähemann
2015-03-29 15:25 ` Joël Krähemann
2015-03-30 7:27 ` Clemens Ladisch [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=5518FAE6.1010308@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=weedlight@gmail.com \
/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