From: Dave Hansen <haveblue@us.ibm.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Patrick Mansfield <patmans@us.ibm.com>,
Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Degraded I/O performance, since 2.5.41
Date: Thu, 10 Oct 2002 17:53:52 -0700 [thread overview]
Message-ID: <3DA62120.9070609@us.ibm.com> (raw)
In-Reply-To: 20021011004227.GA27073@redhat.com
Doug Ledford wrote:
> I try to keep the drivers working
> at a basic level, but until I'm done, benchmarking is pretty much a waste
> of time I think)
Benchmarking is integral in what we're doing right now. We need to
make quick decisions about what is good or bad before the freeze.
This patch makes my machine unusable for anything that isn't in the
pagecache. A simple "make oldconfig" on a cold tree takes minutes to
complete. My grep test got an order of magnitude worse. If we have
to keep this code, can we just make the default queue HUGE for now?
Will that work around it?
A bunch of the AIO people use QLogic cards, which I'm sure are broken
by this as well. I'm going to back this patch out for all the testing
trees I do, and I suggest anyone who cares about I/O on SCSI
(excluding aic7xxx) after 2.5.41 do the same.
--
Dave Hansen
haveblue@us.ibm.com
next parent reply other threads:[~2002-10-11 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210092015170.9790-100000@home.transmeta.com>
[not found] ` <3DA61041.9080808@us.ibm.com>
[not found] ` <20021011004227.GA27073@redhat.com>
2002-10-11 0:53 ` Dave Hansen [this message]
2002-10-11 1:45 ` Degraded I/O performance, since 2.5.41 Dave Hansen
2002-10-11 13:49 Jeffery, David
2002-10-12 17:47 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 1:09 Dave Hansen
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=3DA62120.9070609@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=torvalds@transmeta.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