public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Karel Kulhavy <clock@twibright.com>, linux-kernel@vger.kernel.org
Subject: Re: software mixing in alsa
Date: Wed, 18 May 2005 13:47:17 -0400	[thread overview]
Message-ID: <1116438438.4866.1.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.58.0505181540440.1840@pnote.perex-int.cz>

On Wed, 2005-05-18 at 15:53 +0200, Jaroslav Kysela wrote:
> On Wed, 18 May 2005, Karel Kulhavy wrote:
> 
> > On Tue, May 17, 2005 at 04:36:30PM -0400, Lee Revell wrote:
> > 
> > [...]
> > 
> > > alsa-lib, which is part of userspace.  From the application's point of
> > > view, it does not matter whether the mixing happens in kernel or not.
> > > ALSA follows the philosophy of doing as little as possible in the
> > > kernel, and since mixing and volume control work fine in userspace,
> > > that's where they live.
> > 
> > Mixing is IMHO action that should be in kernel because
> > 
> > 1) needs realtime scheduling to keep latency down
> 
> With a realtime scheduler and properly written drivers (no "schedule"  
> gaps) you'll reach same results. For x86 we use special instructions like
> xchg and locking-free algorithm in dmix, so the latency is SAME for all 
> concurent apps with minimal overhead..

Also doing it in userspace lets us use SSE/MMX.

Lee


  reply	other threads:[~2005-05-18 17:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  9:56 software mixing in alsa Karel Kulhavy
2005-05-17 10:08 ` Jan Spitalnik
2005-05-17 14:13   ` Karel Kulhavy
2005-05-17 18:32     ` Lee Revell
2005-05-17 19:24       ` Karel Kulhavy
2005-05-17 19:32         ` Lee Revell
2005-05-17 20:27         ` Valdis.Kletnieks
2005-05-17 20:36           ` Lee Revell
2005-05-18 13:32             ` Karel Kulhavy
2005-05-18 13:53               ` Jaroslav Kysela
2005-05-18 17:47                 ` Lee Revell [this message]
2005-05-18  6:30           ` ross
2005-05-18  8:42             ` Lee Revell
2005-05-18 13:21             ` Karel Kulhavy
2005-05-18 13:50             ` Nix
2005-05-18 13:48           ` Takashi Iwai
2005-05-18 14:38             ` Pierre Ossman
2005-05-18 18:25               ` Lee Revell
2005-05-19 15:10               ` Valdis.Kletnieks
2005-05-18  9:22         ` Pavel Machek
2005-05-17 19:28       ` Michal Schmidt
2005-05-17 21:04         ` Karel Kulhavy
2005-05-17 21:36           ` Lee Revell
2005-05-17 23:32             ` Lee Revell
2005-05-18 13:44               ` Takashi Iwai

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=1116438438.4866.1.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox