From: Wes Janzen <superchkn@sbcglobal.net>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Con Kolivas <kernel@kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]O18int
Date: Wed, 27 Aug 2003 18:02:49 -0500 [thread overview]
Message-ID: <3F4D3899.1010207@sbcglobal.net> (raw)
In-Reply-To: <1061592027.13091.2.camel@teapot.felipe-alfaro.com>
Felipe Alfaro Solana wrote:
>I have been using 2.6.0-test3-mm3 plus O18int for a whole day and I must
>say that, for me, O18int is the best I've seen until date. I dare to say
>I think it's even better than O10int.
>
I'll second that, the priority inversion issues I was having with
2.6.0-test3-mm2 are completely gone! I haven't been able to get any
serious inversion issues to bring the system to its knees yet, but I'll
keep trying. The only difference is that I've disabled sound in order
to use the latest kernels, but I don't think that probably had anything
to do with the inversion problems I was running into.
And after using 2.6.0-test4 vanilla for a few hours I have a new
appreciation for the improvements that come with Con's patches...
-Wes-
prev parent reply other threads:[~2003-08-27 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 12:31 [PATCH]O18int Con Kolivas
2003-08-22 13:41 ` [PATCH]O18int Wiktor Wodecki
2003-08-22 13:51 ` [PATCH]O18int Con Kolivas
2003-08-22 14:56 ` [PATCH]O18int Wiktor Wodecki
[not found] ` <200308230103.19724.kernel@kolivas.org>
2003-08-22 15:46 ` [PATCH]O18int Wiktor Wodecki
2003-08-22 15:54 ` [PATCH]O18int Con Kolivas
2003-08-22 17:53 ` [PATCH]O18int Mike Fedyk
[not found] ` <200308222335.50318.insecure@mail.od.ua>
2003-08-22 20:44 ` [PATCH]O18int Wiktor Wodecki
2003-08-22 21:04 ` [PATCH]O18int Mike Fedyk
2003-08-22 22:40 ` [PATCH]O18int Felipe Alfaro Solana
2003-08-27 23:02 ` Wes Janzen [this message]
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=3F4D3899.1010207@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=felipe_alfaro@linuxmail.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/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