All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schoenleitner <dev.c0debabe@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Are ALSA io plugins implemented as threads or does ALSA use fork() ?
Date: Fri, 19 Mar 2010 16:20:44 +0100	[thread overview]
Message-ID: <4BA3964C.4000603@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1003191530230.3925@eeebox2.perex-int.cz>

Jaroslav Kysela wrote:
> On Fri, 19 Mar 2010, Stefan Schoenleitner wrote:
>> * Are these instances running as separate processes (i.e. fork()) or are
>> they implemented as threads ? How is this implemented internally in the
>> ALSA code ?
> 
> No forks or threads. Both instances will run in one process with the
> audio application. The plugin code must take core how many pcm instances
> are active and send the appropriate communication file descriptors to
> application for select/poll I/O multiplexing.

Thanks for the quick answer, I have a better understanding of the plugin
concept now.

cheers,
Stefan

      reply	other threads:[~2010-03-19 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 14:20 Are ALSA io plugins implemented as threads or does ALSA use fork() ? Stefan Schoenleitner
2010-03-19 14:44 ` Jaroslav Kysela
2010-03-19 15:20   ` Stefan Schoenleitner [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=4BA3964C.4000603@gmail.com \
    --to=dev.c0debabe@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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.