From: "Michael B Allen" <mba2000@ioplex.com>
To: "Marc-Christian Petersen" <m.c.p@wolk-project.de>
Cc: 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 05:35:02 -0400 (EDT) [thread overview]
Message-ID: <38291.207.172.171.44.1051004102.squirrel@miallen.com> (raw)
In-Reply-To: <200304221006.09601.m.c.p@wolk-project.de>
> On Tuesday 22 April 2003 09:48, Michael B Allen wrote:
>
> Hi Michael,
>
>> I'm running Red Hat 7.3 with their stock 2.4.18-3 kernel on an IBM
>> T30. Once every few hours X locks up for 5-10 seconds while the disk
>> grinds. If I type in an Xterm the characters are not echoed until the
<snip>
>> I would like very much for this behavior to go away as it is extremely
>> annoying. If there is a patch please let me know where I can get it.
> There are some hacks. One by Andrea Arcangeli, one by Neil Schemenauer and
> one
> by Con Kolivas and me. Search the archives please (lowlat elevator/io
> scheduler)
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?
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?
Thanks,
Mike
PS: Why are there only "hacks"? Is this not considered important?
next prev parent reply other threads:[~2003-04-22 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:48 Michael B Allen
2003-04-22 8:06 ` Marc-Christian Petersen
2003-04-22 9:35 ` Michael B Allen [this message]
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
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=38291.207.172.171.44.1051004102.squirrel@miallen.com \
--to=mba2000@ioplex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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®