From: Andrew Morton <akpm@digeo.com>
To: Jens Axboe <axboe@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] deadline io scheduler
Date: Thu, 26 Sep 2002 00:12:41 -0700 [thread overview]
Message-ID: <3D92B369.7AFD28D4@digeo.com> (raw)
In-Reply-To: 3D92A61E.40BFF2D0@digeo.com
Andrew Morton wrote:
>
> I'll test scsi now.
>
aic7xxx, Fujitsu "MAF3364L SUN36G" (36G SCA-2)
Maximum number of TCQ tags=253
fifo_batch time cat kernel/*.c (seconds)
64 58
32 54
16 20
8 58
4 1:15
2 53
Maximum number of TCQ tags=4
fifo_batch time cat kernel/*.c (seconds)
64 53
32 39
16 33
8 21
4 22
2 36
1 22
Maximum number of TCQ tags = 0:
fifo_batch time cat kernel/*.c (seconds)
64 22
32 10.3
16 10.5
8 5.5
4 3.2
2 1.9
I selected fifo_batch=16 and altered writes_starved and read_expires
again. They made no appreciable difference.
>From this I can only conclude that my poor little read was stuck
in the disk for ages while TCQ busily allowed new incoming writes
to bypass already-sent reads.
A dreadful misdesign. Unless we can control this with barriers,
and if Fujutsu is typical, TCQ is just uncontrollable. I, for
one, would not turn it on in a pink fit.
next prev parent reply other threads:[~2002-09-26 7:07 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 17:20 [PATCH] deadline io scheduler Jens Axboe
2002-09-26 6:15 ` Andrew Morton
2002-09-26 6:27 ` David S. Miller
2002-09-26 6:44 ` Jens Axboe
2002-09-26 6:59 ` Jens Axboe
2002-09-26 7:06 ` William Lee Irwin III
2002-09-26 7:06 ` David S. Miller
2002-09-26 7:16 ` Jeff Garzik
2002-09-26 7:13 ` David S. Miller
2002-09-26 7:33 ` Jeff Garzik
2002-09-26 7:35 ` David S. Miller
2002-09-26 8:15 ` Michael Clark
2002-09-26 8:18 ` William Lee Irwin III
2002-09-26 17:41 ` Mike Anderson
2002-09-26 18:03 ` Jeff Garzik
2002-09-26 19:21 ` Mike Anderson
2002-09-27 5:41 ` Andrew Vasquez
2002-09-27 5:57 ` Jeff Garzik
2002-09-27 16:58 ` Mike Anderson
2002-09-26 22:41 ` Matt Porter
2002-09-26 22:35 ` Mark Bellon
2002-09-26 20:21 ` Thomas Tonino
2002-09-26 7:41 ` Jeff Garzik
2002-09-26 7:23 ` William Lee Irwin III
2002-09-26 7:11 ` Jeff Garzik
2002-09-26 7:14 ` William Lee Irwin III
2002-09-26 15:54 ` Patrick Mansfield
2002-09-30 8:15 ` Jens Axboe
2002-09-30 15:39 ` Patrick Mansfield
2002-09-30 16:08 ` Jens Axboe
2002-09-26 8:28 ` Daniel Pittman
2002-09-26 8:29 ` Jens Axboe
2002-09-26 23:23 ` Daniel Pittman
2002-09-30 8:10 ` Jens Axboe
2002-09-26 15:09 ` Rik van Riel
2002-09-26 7:12 ` Andrew Morton [this message]
2002-09-26 7:17 ` Jens Axboe
2002-09-26 7:34 ` Jens Axboe
2002-09-30 7:45 ` Pavel Machek
2002-10-02 5:35 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2002-09-27 16:01 Andrew Vasquez
2002-09-27 17:07 ` Mike Anderson
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=3D92B369.7AFD28D4@digeo.com \
--to=akpm@digeo.com \
--cc=axboe@suse.de \
--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