Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932740AbWAHNjl (ORCPT ); Sun, 8 Jan 2006 08:39:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932737AbWAHNjl (ORCPT ); Sun, 8 Jan 2006 08:39:41 -0500 Received: from outgoing.tpinternet.pl ([193.110.120.20]:45459 "EHLO outgoing.tpinternet.pl") by vger.kernel.org with ESMTP id S932732AbWAHNjk (ORCPT ); Sun, 8 Jan 2006 08:39:40 -0500 In-Reply-To: References: <20060104030034.6b780485.zaitcev@redhat.com> <20060108020335.GA26114@dspnet.fr.eu.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <20198DF8-D632-412C-9FDA-DE0F3FC1D68B@neostrada.pl> Cc: Olivier Galibert , Takashi Iwai , ALSA development , linux-sound@vger.kernel.org, LKML Content-Transfer-Encoding: 7bit From: Marcin Dalecki Subject: Re: [OT] ALSA userspace API complexity Date: Sun, 8 Jan 2006 14:38:56 +0100 To: Jaroslav Kysela X-Mailer: Apple Mail (2.746.2) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 753 Lines: 19 On 2006-01-08, at 10:42, Jaroslav Kysela wrote: >> >> Once again no. Nothing prevents the kernel to forward the data to >> userland daemons depending on a userspace-uploaded configuration. > > But it's quite ineffecient. The kernel must switch tasks at least > twice > or more. It's the major problem with the current OSS API. 1. It was only presented as an opportunity. Not every data has to go this way. 2. Aren't you the person which was showing off X11 as a good example to draw guidelines from? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/