lkml.org 
[lkml]   [2006]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [OT] ALSA userspace API complexity
    On Sun, Jan 08, 2006 at 10:42:02AM +0100, Jaroslav Kysela wrote:
    > On Sun, 8 Jan 2006, Olivier Galibert wrote:
    >
    > > On Sat, Jan 07, 2006 at 03:32:27PM +0100, Takashi Iwai wrote:
    > > > Yes, it's a known problem to be fixed. But, it's no excuse to do
    > > > _everything_ in the kernel (which OSS requires).
    > >
    > > OSS does not require to do anything in the kernel except an entry
    > > point.
    > >
    > >
    > > > 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.
    >
    > 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.

    Once. U->K or K->U is not task switching and accordingly has a very
    low cost. It's changing of userspace task that is costly. And dmix
    _is_ a task switch, there is no performance difference between talking
    with it through shared memory and semaphores and who knows what else
    and talking with it through a kernel interface.

    You should count how many U-U switches and U-K syscalls communicating
    with dmix represents. Hard to do for a simple user, since the
    protocol is not documented.

    OG.

    -
    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/

    \
     
     \ /
      Last update: 2006-01-08 14:07    [W:0.020 / U:151.512 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site