From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: "Michael B Allen" <mba2000@ioplex.com>
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 11:59:39 +0200 [thread overview]
Message-ID: <200304221155.56841.m.c.p@wolk-project.de> (raw)
In-Reply-To: <38291.207.172.171.44.1051004102.squirrel@miallen.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Tuesday 22 April 2003 11:35, Michael B Allen wrote:
Hi Michael,
> 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
Then you are not able to search archives.
http://marc.theaimsgroup.com/?l=linux-kernel&m=105092498721316&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=105060066815681&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=103835185429978&w=2
The 3rd url has a config option. Same attached w/o config option.
> 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?
there were some complaints. Anyway, if it's important or not depends on the
point of view. For me, it is _mega_ important, for mainline 2.4, I don't
think it is 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?
Look for a patch that adds "2.4.19-pre*".
> PS: Why are there only "hacks"? Is this not considered important?
Well, the attached one is really a hack. It drops throughput ~20-30 % but gets
rid of all the annyoing pauses/stops while disk i/o. The 2 other approaches
are no real hacks though they also drop throughput.
You can also try "elvtune -r 0 -w 8192 /dev/bla" and see if it makes any
difference if you don't want to patch anything.
ciao, Marc
[-- Attachment #2: lowlat-elevator-hack.patch --]
[-- Type: text/x-diff, Size: 950 bytes --]
--- old/drivers/block/ll_rw_blk.c 2002-12-18 01:03:50.000000000 +0100
+++ new/drivers/block/ll_rw_blk.c 2003-04-22 11:49:36.000000000 +0200
@@ -432,9 +432,7 @@ static void blk_init_free_list(request_q
si_meminfo(&si);
megs = si.totalram >> (20 - PAGE_SHIFT);
- nr_requests = 128;
- if (megs < 32)
- nr_requests /= 2;
+ nr_requests = 4;
blk_grow_request_list(q, nr_requests);
init_waitqueue_head(&q->wait_for_requests[0]);
--- old/include/linux/elevator.h 2002-12-18 01:03:59.000000000 +0100
+++ new/include/linux/elevator.h 2003-04-22 11:49:58.000000000 +0200
@@ -93,8 +93,8 @@ static inline int elevator_request_laten
#define ELEVATOR_LINUS \
((elevator_t) { \
- 2048, /* read passovers */ \
- 8192, /* write passovers */ \
+ 0, /* read passovers */ \
+ 0, /* write passovers */ \
\
elevator_linus_merge, /* elevator_merge_fn */ \
elevator_linus_merge_req, /* elevator_merge_req_fn */ \
next prev parent reply other threads:[~2003-04-22 9:47 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 [this message]
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=200304221155.56841.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--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