From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.38-mm2
Date: Mon, 23 Sep 2002 09:16:33 +0200 [thread overview]
Message-ID: <20020923071633.GA15479@suse.de> (raw)
In-Reply-To: <3D8E96AA.C2FA7D8@digeo.com>
On Sun, Sep 22 2002, Andrew Morton wrote:
> +read-latency.patch
>
> Fix the writer-starves-reader elevator problem. This is basically
> the read_latency2 patch from -ac kernels.
>
> On IDE it provides a 100x improvement in read throughput when there
> is heavy writeback happening. 40x on SCSI. You need to disable
Ah interesting. I do still think that it is worth to investigate _why_
both elevator_linus and deadline does not prevent the read starvation.
The read-latency is a hack, not a solution imo.
> tagged command queueing on scsi - it appears to be quite stupidly
> implemented.
Ahem I think you are being excessively harsh, or maybe passing judgement
on something you haven't even looked at. Did you consider that you
_drive_ may be the broken component? Excessive turn-around times for
request when using deep tcq is not unusual, by far.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.38-mm2
Date: Mon, 23 Sep 2002 09:16:33 +0200 [thread overview]
Message-ID: <20020923071633.GA15479@suse.de> (raw)
In-Reply-To: <3D8E96AA.C2FA7D8@digeo.com>
On Sun, Sep 22 2002, Andrew Morton wrote:
> +read-latency.patch
>
> Fix the writer-starves-reader elevator problem. This is basically
> the read_latency2 patch from -ac kernels.
>
> On IDE it provides a 100x improvement in read throughput when there
> is heavy writeback happening. 40x on SCSI. You need to disable
Ah interesting. I do still think that it is worth to investigate _why_
both elevator_linus and deadline does not prevent the read starvation.
The read-latency is a hack, not a solution imo.
> tagged command queueing on scsi - it appears to be quite stupidly
> implemented.
Ahem I think you are being excessively harsh, or maybe passing judgement
on something you haven't even looked at. Did you consider that you
_drive_ may be the broken component? Excessive turn-around times for
request when using deep tcq is not unusual, by far.
--
Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-23 7:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 4:20 2.5.38-mm2 Andrew Morton
2002-09-23 4:20 ` 2.5.38-mm2 Andrew Morton
2002-09-23 7:16 ` Jens Axboe [this message]
2002-09-23 7:16 ` 2.5.38-mm2 Jens Axboe
2002-09-23 7:43 ` 2.5.38-mm2 Andrew Morton
2002-09-23 7:43 ` 2.5.38-mm2 Andrew Morton
2002-09-24 21:10 ` 2.5.38-mm2 Bill Davidsen
2002-09-24 21:10 ` 2.5.38-mm2 Bill Davidsen
2002-09-23 9:45 ` 2.5.38-mm2 [PATCH] Dipankar Sarma
2002-09-23 9:45 ` Dipankar Sarma
2002-09-23 16:28 ` Andrew Morton
2002-09-23 16:28 ` Andrew Morton
2002-09-23 17:33 ` Dipankar Sarma
2002-09-23 17:33 ` Dipankar Sarma
2002-09-24 4:41 ` Rusty Russell
2002-09-24 4:41 ` Rusty Russell
2002-09-24 10:24 ` Dipankar Sarma
2002-09-24 10:24 ` Dipankar Sarma
2002-09-24 14:56 ` Rusty Russell
2002-09-24 14:56 ` Rusty Russell
2002-09-23 9:56 ` 2.5.38-mm2 [PATCH] (dcache) Dipankar Sarma
2002-09-23 9:56 ` Dipankar Sarma
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=20020923071633.GA15479@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.