public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Silviu Marin-Caea <silviu_marin-caea@fieldinsights.ro>
Cc: opensuse-factory@opensuse.org, linux-kernel@vger.kernel.org
Subject: Re: [opensuse-factory] Re[2]: 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded
Date: Tue, 07 Mar 2006 17:10:21 -0500	[thread overview]
Message-ID: <1141769422.767.99.camel@mindpipe> (raw)
In-Reply-To: <200603070942.31774.silviu_marin-caea@fieldinsights.ro>

On Tue, 2006-03-07 at 09:42 +0200, Silviu Marin-Caea wrote:
> On Monday 06 March 2006 14:47, s.schmidt@avm.de wrote:
> 
> > Even though people might do realtime DSP things in user space with Linux
> > and soft modems might work pretty well in userspace, in the case of Fax G3
> > an extremely short latency is required.
> 
> So basically we have to choose between:
> 
> 1. keeping a stable open source kernel and sticking to the principles that got 
> Linux where it is now
> 
> and
> 
> 2. Fax G3
> 
> Umm...

Extremely short, consistent latency is also required to use a Linux box
as a live audio effects processor and thousands of people do that.  It
works extremely well, is used by numerous professionals, and no one has
ever seriously proposed moving it to the kernel.  The POSIX realtime
APIs were designed for exactly this kind of application.

If they are doing serious realtime DSP then they should get better
results in userspace anyway, because they get to use the floating point
unit which isn't allowed in the kernel.

I suspect you last tried it in the 2.4 or early 2.6 era when patching
the kernel was required to get decent latency.

Lee


  reply	other threads:[~2006-03-07 22:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200601200904.00389.dazzle.digital@gmail.com>
2006-02-03 16:24 ` 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded s.schmidt
2006-02-03 22:50   ` Pavel Machek
2006-02-04 16:27   ` Valdis.Kletnieks
2006-02-04 19:24     ` Jan Kiszka
2006-02-09 15:52       ` Jan Engelhardt
2006-02-05 20:53   ` Greg KH
2006-02-16 14:24     ` Re[2]: " s.schmidt
2006-02-16 14:35       ` Arjan van de Ven
2006-02-16 19:49       ` [opensuse-factory] " Robert Schiele
2006-02-16 22:09       ` Carl-Daniel Hailfinger
2006-02-16 22:51         ` Karsten Keil
2006-02-17 23:00       ` Greg KH
2006-02-19 14:34         ` Stephan von Krawczynski
2006-03-06 12:47         ` Re[2]: " s.schmidt
2006-03-06 17:05           ` Greg KH
2006-03-06 21:09             ` [Libusb-devel] " Michael Bender
2006-03-06 22:02               ` Greg KH
2006-03-07  7:42           ` [opensuse-factory] Re[2]: " Silviu Marin-Caea
2006-03-07 22:10             ` Lee Revell [this message]
2006-03-07 23:37               ` Matthias Andree
2006-03-08  0:55                 ` Lee Revell
2006-03-08  1:39                   ` Douglas McNaught
2006-02-18  2:42       ` Lee Revell
2006-02-19  4:57       ` Sasha Khapyorsky
2006-02-19 17:02         ` Steven Rostedt
2006-02-20  3:11           ` Sasha Khapyorsky
2006-02-20  6:58             ` Steven Rostedt
2006-02-19 16:25       ` Re[2]: " Christoph Hellwig
2006-02-19  3:09     ` Anton Blanchard
2006-02-19  3:20       ` Greg KH

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=1141769422.767.99.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-factory@opensuse.org \
    --cc=silviu_marin-caea@fieldinsights.ro \
    /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