From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: Which transfer mode to use Date: Wed, 14 Oct 2009 16:44:44 +0200 Message-ID: <4AD5E3DC.5070701@ladisch.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by alsa0.perex.cz (Postfix) with ESMTP id 90FED243FF for ; Wed, 14 Oct 2009 16:44:46 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Till Crueger Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Till Crueger wrote: > 1. Asynchronous callback: > This method seems to be the best explained by all the tutorials I could > find, so I am guessing this is the best choice for audio applications. It's the worst choice; it isn't available on many devices, and the asynchronous callback cannot do much because it might have interrupted some non-reentrant function. > 2. read/write: > So far this seems the best choice. Use it. > For this however I would have to figure out after each polling, how > much data can be written. snd_pcm_avail() > I found some concerns about differences in lattency between these > three methods. Those concerned have not measured; the latency is _exactly_ the same. HTH Clemens