All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Schnell" <daniel.schnell@gmx.net>
To: alsa-devel@lists.sourceforge.net
Subject: Q: is the ALSA-lib API thread-safe
Date: Thu, 5 Aug 2004 09:57:00 +0200	[thread overview]
Message-ID: <1e2101c47ac1$ca702340$2c0aa8c0@lumpidu> (raw)

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

Hi,

is the ALSA-Lib-API thread-safe concerning the following scenario:


in thread 1 the audio-processing takes place via snd_pcm_avail_update(), 
snd_pcm_begin(), snd_pcm_commit(). In thread 2 I call the functions: 
snd_pcm_hwsync(), snd_pcm_avail_update() to get the actual delay via
bufferframes - snd_pcm_avail_update(). Should I lock these calls or
should I use instead snd_pcm_avail() in thread 2 ?
Is there any difference concerning thread-safety between the hw: layer or the plug: layer ?

Confused,

Ciao,

Daniel.

[-- Attachment #2: Type: text/html, Size: 1369 bytes --]

             reply	other threads:[~2004-08-05  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  7:57 Daniel Schnell [this message]
2004-08-05 10:06 ` Q: is the ALSA-lib API thread-safe Clemens Ladisch
2004-08-05 12:31   ` Paul Davis
2004-08-05 12:51     ` Jaroslav Kysela

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='1e2101c47ac1$ca702340$2c0aa8c0@lumpidu' \
    --to=daniel.schnell@gmx.net \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.