From: Dave Hansen <haveblue@us.ibm.com>
To: linux-scsi@vger.kernel.org
Subject: Re: Degraded I/O performance, since 2.5.41
Date: Thu, 10 Oct 2002 16:48:47 -0700 [thread overview]
Message-ID: <3DA611DF.3000206@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210092015170.9790-100000@home.transmeta.com
Linus Torvalds wrote:
> In article <3DA4D34F.3070106@us.ibm.com> you write:
>
>>When I run a certain large webserver benchmark, I prefer to warm the
>>pagecache up with the file set first, to cheat a little :) I grep
>>through 20 different 500MB file sets in parallel to do this. It is
>>a _lot_ slower in the BK snapshot than in plain 2.5.41.
>
> Can you pinpont where this started happening? There aren't that many
> changes since 2.5.41 that I'd consider suspicious, and it would
help > to try to pinpoint it a bit.
Using stupid brute force, I narrowed it down to 12 patches. The only
one that touches generic SCSI code is the queue length one.
1.704.1.2, in my tree from dledford@redhat.com. Backing it out fixed
my problem. CC'ing him...
I would guess that it's just making stupid, er.... suboptimal,
decisions about the length for my hardware. With a controller as
"smart" as the ServeRAID, I would imagine the best approach is to just
throw as many requests at it at one time as you can, then let the
controller sort it out. Doug, I noticed that you changed a bunch of
code to the aic7xxx_old driver, is this just a lack of optimization in
the ServeRAID driver?
--
Dave Hansen
haveblue@us.ibm.com
next parent reply other threads:[~2002-10-10 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210092015170.9790-100000@home.transmeta.com>
2002-10-10 23:48 ` Dave Hansen [this message]
2002-10-10 23:54 ` Degraded I/O performance, since 2.5.41 James Bottomley
2002-10-11 1:09 ` James Bottomley
2002-10-11 1:59 ` Doug Ledford
2002-10-17 5:52 ` block TCQ [was: Re: Degraded I/O performance, since 2.5.41] Luben Tuikov
2002-10-11 13:49 Degraded I/O performance, since 2.5.41 Jeffery, David
2002-10-12 17:47 ` 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=3DA611DF.3000206@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).