All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Kulhavy <clock@twibright.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: software mixing in alsa
Date: Wed, 18 May 2005 15:32:15 +0200	[thread overview]
Message-ID: <20050518133215.GB13736@kestrel> (raw)
In-Reply-To: <1116362191.32210.24.camel@mindpipe>

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
2) needs tight cooperation with the hardware to prevent dropouts
on underruns
3) Is a trivial linear algorithm involving memory blocks and linear
   arithmetic, no complicated computations that are difficult to
   check for BugFree(TM) so shouldn't present a great risk on kernel
   stability
4) Fits into the kernel philosophy. Kernel is a program meant to provide
   time-sharing access to limited hardware resource. Sound card is a
   limited hardware resource.
5) From the knowledge of the exact hardware, the mixing routine in
   kernel can know maximum allowable levels etc. to prevent clipping.
   

CL<

  reply	other threads:[~2005-05-18 13:35 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 [this message]
2005-05-18 13:53               ` Jaroslav Kysela
2005-05-18 17:47                 ` Lee Revell
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=20050518133215.GB13736@kestrel \
    --to=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.