From: J Sloan <joe@tmsusa.com>
To: Michael B Allen <mba2000@ioplex.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: What's the deal McNeil? Bad interactive behavior in X w/ RH's 2.4.18
Date: Tue, 22 Apr 2003 20:31:44 -0700 [thread overview]
Message-ID: <3EA60920.8090800@tmsusa.com> (raw)
In-Reply-To: 38291.207.172.171.44.1051004102.squirrel@miallen.com
Michael B Allen wrote:
>Ok, I searched a little using the Googler at indiana.edu's archives but
>nothing jumped up and bit me. I'm not too excited about applying a patch
>snarfed out of an e-mail anywat. I'm surprised no one else has not
>complained about this enough to the point where you guys don't have a
>canned answer with a link. Is this problem not considered important?
>
Yes, the link is www.redhat.com/errata
But yes, for those who like to roll their
own, Con's responsiveness patchset is
farily well regarded and trusted - you
can grab it from kernel.kolivas.org -
I've had good results with just the 001,
002 and 003 patches on stock 2.4.20 -
>
>Does anyone know which RH patch in the 2.4.18-10 RPM adds this elevator
>throughput "improvement"? What identifiers would such a patch have in it?
>
>
2.4.18-10?
You want 2.4.18-27.7x - in other words, the
current redhat kernel for your release.
The patches are all in the kernel srpm for
you to view and analyze...
BTW If you really want low latency you'll
love 2.6
Joe
next prev parent reply other threads:[~2003-04-23 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:48 What's the deal McNeil? Bad interactive behavior in X w/ RH's 2.4.18 Michael B Allen
2003-04-22 8:06 ` Marc-Christian Petersen
2003-04-22 9:35 ` Michael B Allen
2003-04-22 9:56 ` jw schultz
2003-04-22 14:06 ` Alan Cox
2003-04-22 9:59 ` Marc-Christian Petersen
2003-04-23 3:31 ` J Sloan [this message]
2003-04-22 14:19 ` Alan Cox
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=3EA60920.8090800@tmsusa.com \
--to=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mba2000@ioplex.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