From: Ondrej Zary <linux@rainbow-software.org>
To: Jens Axboe <axboe@suse.de>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"André Tomt" <andre@tomt.net>, "Al Boldi" <a1426z@gawab.com>,
"'Bartlomiej Zolnierkiewicz'" <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] IDE update
Date: Tue, 05 Jul 2005 23:39:25 +0200 [thread overview]
Message-ID: <42CAFE0D.1070909@rainbow-software.org> (raw)
In-Reply-To: <20050705191448.GB30235@suse.de>
Jens Axboe wrote:
> On Tue, Jul 05 2005, Linus Torvalds wrote:
>
>>
>>On Tue, 5 Jul 2005, Jens Axboe wrote:
>>
>>>Looks interesting, 2.6 spends oodles of times copying to user space.
>>>Lets check if raw reads perform ok, please try and time this app in 2.4
>>>and 2.6 as well.
>>
>>I think it's just that 2.4.x used to allow longer command queues. I think
>>MAX_NR_REQUESTS is 1024 in 2.4.x, and just 128 in 2.6.x or something like
>>that.
>
>
> But for this case, you only have one command in flight. hdparm is highly
> synchronous, my oread case is as well.
>
>
>>Also, the congestion thresholds are questionable: we consider a queue
>>congested if it is within 12% of full, but then we consider it uncongested
>>whenever it falls to within 18% of full, which I bet means that for some
>>streaming loads we have just a 6% "window" that we keep adding new
>>requests to (we wait when we're almost full, but then we start adding
>>requests again when we're _still_ almost full). Jens, we talked about this
>>long ago, but I don't think we ever did any timings.
>
>
> In theory, the ioc batching should handle that case. But as you can see
> from recent commits, I'm not very happy with how this currently works.
> It should not impact this testing, though.
>
>
>>Making things worse, things like this are only visible on stupid hardware
>>that has long latencies to get started (many SCSI controllers used to have
>>horrid latencies), so you'll never even see any difference on a lot of
>>hardware.
>
>
> IDE still has much lower overhead per command than your average SCSI
> hardware. SATA with FIS even improves on this, definitely a good thing!
>
>
>>It's probably worth testing with a bigger request limit. I forget what the
>>/proc interfaces are (and am too lazy to look it up), Jens can tell us ;)
>
>
> It's /sys/block/<device>/queue/nr_requests now, can be changed at will.
>
Tested with default 128, 1024 and 4 (minimum) and no change.
--
Ondrej Zary
next prev parent reply other threads:[~2005-07-05 21:39 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 16:52 [git patches] IDE update Bartlomiej Zolnierkiewicz
2005-07-04 12:01 ` Al Boldi
2005-07-04 12:30 ` Bartlomiej Zolnierkiewicz
2005-07-04 15:30 ` Al Boldi
2005-07-04 15:41 ` Bartlomiej Zolnierkiewicz
2005-07-04 17:06 ` Al Boldi
2005-07-04 17:38 ` Ondrej Zary
2005-07-04 19:51 ` Bartlomiej Zolnierkiewicz
2005-07-04 20:32 ` Al Boldi
2005-07-04 20:47 ` Bartlomiej Zolnierkiewicz
2005-07-04 23:25 ` André Tomt
2005-07-05 3:43 ` IOWAIT block layer problem Al Boldi
2005-07-05 10:01 ` [git patches] IDE update Ondrej Zary
2005-07-05 10:14 ` Jens Axboe
2005-07-05 10:19 ` Ondrej Zary
2005-07-05 10:42 ` Jens Axboe
2005-07-05 12:35 ` Ondrej Zary
2005-07-05 12:51 ` Jens Axboe
2005-07-05 13:02 ` Ondrej Zary
2005-07-05 13:11 ` Jens Axboe
2005-07-05 15:51 ` Ondrej Zary
2005-07-05 14:21 ` Jens Axboe
2005-07-05 15:00 ` Ondrej Zary
2005-07-05 19:18 ` Jens Axboe
2005-07-05 19:25 ` Jens Axboe
2005-07-05 21:36 ` Ondrej Zary
2005-07-05 17:27 ` Linus Torvalds
2005-07-05 19:14 ` Jens Axboe
2005-07-05 21:39 ` Ondrej Zary [this message]
2005-07-11 14:21 ` Alan Cox
2005-07-06 0:35 ` Grant Coady
2005-07-06 0:51 ` Linus Torvalds
2005-07-06 3:26 ` Al Boldi
2005-07-06 4:56 ` Grant Coady
2005-07-06 5:22 ` Linus Torvalds
2005-07-08 8:48 ` Jens Axboe
2005-07-08 10:20 ` Ingo Molnar
2005-07-08 11:45 ` Jens Axboe
2005-07-07 22:32 ` Mark Lord
2005-07-08 0:06 ` Grant Coady
2005-07-08 11:37 ` Erik Slagter
2005-07-06 20:56 ` Bill Davidsen
2005-07-07 13:47 ` Ondrej Zary
2005-07-07 13:48 ` Bartlomiej Zolnierkiewicz
2005-07-07 19:34 ` Bill Davidsen
2005-07-05 2:47 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 21:37 [git patches] ide update Bartlomiej Zolnierkiewicz
2005-08-18 22:15 ` Linus Torvalds
2005-08-18 22:19 ` Nish Aravamudan
2005-08-19 0:44 ` Mark Lord
2005-08-18 23:08 ` Alan Cox
2005-08-19 9:02 ` Bartlomiej Zolnierkiewicz
2005-08-19 18:06 ` Alan Cox
2005-08-19 23:51 ` Bartlomiej Zolnierkiewicz
2005-08-19 23:52 ` Bartlomiej Zolnierkiewicz
2005-11-10 1:00 Bartlomiej Zolnierkiewicz
2005-11-18 23:21 Bartlomiej Zolnierkiewicz
2005-11-19 23:46 Bartlomiej Zolnierkiewicz
2005-12-15 2:03 Bartlomiej Zolnierkiewicz
2007-05-09 22:46 [git patches] IDE update Bartlomiej Zolnierkiewicz
2007-05-09 22:46 ` Jeff Garzik
2007-05-09 23:20 ` David Miller
2007-05-09 23:23 ` Bartlomiej Zolnierkiewicz
2007-05-09 23:18 ` Jeff Garzik
2007-05-09 22:47 ` Jeff Garzik
2007-05-09 22:59 ` Andrew Morton
2007-05-09 23:15 ` Jeff Garzik
2007-07-09 21:46 Bartlomiej Zolnierkiewicz
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=42CAFE0D.1070909@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=a1426z@gawab.com \
--cc=andre@tomt.net \
--cc=axboe@suse.de \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).