From: Andrew Morton <akpm@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: mpm@selenic.com, paul@linuxaudiosystems.com,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.X, NPTL, SCHED_FIFO and JACK
Date: Thu, 1 Jul 2004 15:45:54 -0700 [thread overview]
Message-ID: <20040701154554.30063e97.akpm@osdl.org> (raw)
In-Reply-To: <20040701181401.GB21066@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> wrote:
>
> On Thu, Jul 01, 2004 at 01:03:56PM -0500, Matt Mackall wrote:
> > 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.
>
> I appear to have nuked the thread you're replying to in disgust over
> this precise issue.
In fairness, the CPU scheduler has been spinning like a top for a
couple of years, and it still ain't settled.
That's just the one in Linus's tree, let alone the umpteen rewrites which are
floating about.
next prev parent reply other threads:[~2004-07-01 22:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 13:41 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
2004-07-01 18:14 ` William Lee Irwin III
2004-07-01 22:45 ` Andrew Morton [this message]
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=20040701154554.30063e97.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paul@linuxaudiosystems.com \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®