From: Matt Mackall <mpm@selenic.com>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.X, NPTL, SCHED_FIFO and JACK
Date: Thu, 1 Jul 2004 13:03:56 -0500 [thread overview]
Message-ID: <20040701180356.GI5414@waste.org> (raw)
In-Reply-To: <200406301341.i5UDfkKX010518@localhost.localdomain>
On Wed, Jun 30, 2004 at 09:41:46AM -0400, Paul Davis wrote:
> Because of the recognition by kernel developers that 2.6 does not
> perform as well as 2.4+lowlat (the Andrew Morton patches) when it
> comes to scheduling latency, most audio developers and users have
> remained with 2.4. Recently however, several brave souls have
> attempted to test 2.6. The results have been mixed.
I'm afraid these "brave souls" have shown up to the baby shower after
the child's been accepted to college. Developers getting around to
testing 2.6 after multiple vendors are shipping it should not be
characterized as courageous.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-07-01 18:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 13:41 2.6.X, NPTL, SCHED_FIFO and JACK Paul Davis
2004-06-30 15:04 ` Ingo Molnar
2004-06-30 15:18 ` Ingo Molnar
2004-06-30 15:26 ` Jakub Jelinek
2004-06-30 16:32 ` Paul Davis
2004-06-30 16:57 ` Jakub Jelinek
2004-06-30 17:52 ` Paul Davis
2004-06-30 15:05 ` Ingo Molnar
2004-06-30 16:12 ` Paul Davis
2004-06-30 17:07 ` Ulrich Drepper
2004-06-30 17:50 ` Paul Davis
2004-07-01 18:03 ` Matt Mackall [this message]
2004-07-01 18:14 ` William Lee Irwin III
2004-07-01 22:45 ` Andrew Morton
2004-07-02 0:45 ` William Lee Irwin III
2004-07-02 1:38 ` Peter Williams
2004-07-02 2:53 ` William Lee Irwin III
2004-07-02 3:03 ` Con Kolivas
2004-07-02 3:05 ` William Lee Irwin III
2004-07-02 3:27 ` Paul Davis
2004-07-02 7:37 ` William Lee Irwin III
2004-07-02 10:40 ` Takashi Iwai
2004-07-06 0:48 ` Peter Williams
2004-07-02 14:42 ` Paul Davis
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=20040701180356.GI5414@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@linuxaudiosystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox