Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161149AbWAHC0q (ORCPT ); Sat, 7 Jan 2006 21:26:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161150AbWAHC0q (ORCPT ); Sat, 7 Jan 2006 21:26:46 -0500 Received: from kepler.fjfi.cvut.cz ([147.32.6.11]:25063 "EHLO kepler.fjfi.cvut.cz") by vger.kernel.org with ESMTP id S1161148AbWAHC0p (ORCPT ); Sat, 7 Jan 2006 21:26:45 -0500 Date: Sun, 8 Jan 2006 03:26:18 +0100 (CET) From: Martin Drab To: Olivier Galibert cc: Takashi Iwai , ALSA development , linux-sound@vger.kernel.org, LKML Subject: Re: [OT] ALSA userspace API complexity In-Reply-To: <20060108020335.GA26114@dspnet.fr.eu.org> Message-ID: References: <20060104030034.6b780485.zaitcev@redhat.com> <20060108020335.GA26114@dspnet.fr.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1033 Lines: 22 On Sun, 8 Jan 2006, Olivier Galibert wrote: > > And if the application doesn't support, who and where converts it? > > With OSS API, it's a job of the kernel. > > Once again no. Nothing prevents the kernel to forward the data to > userland daemons depending on a userspace-uploaded configuration. I think that the point was, that switching from userspace to kernelspace then to userspace again and back to kernelspace in order to do something, that could have been done directly in the userspace, and though could save those two unnecessary switches, is an unnecessary overhead, which may not necessarily be that insignificant if it's done so often (which for streaming audio is the case). Why doing things complicated when there is no evident gain from it, or is there? Martin - 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/