From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
alex@nibbles.it, bugme-daemon@bugzilla.kernel.org,
Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
linux-scsi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10810] New: Performance regression on DAC960 and kernel 2.6.24+
Date: Wed, 28 May 2008 14:56:51 -0500 [thread overview]
Message-ID: <1212004611.3445.70.camel@localhost.localdomain> (raw)
In-Reply-To: <20080528183725.GD25504@kernel.dk>
On Wed, 2008-05-28 at 20:37 +0200, Jens Axboe wrote:
> On Wed, May 28 2008, James Bottomley wrote:
> > Well, the DAC960 is very old. It has a trick we escaped from in SCSI
> > where if it gets an error in the request it resubmits it a sector at a
> > time. It sounds very much like it's doing that for every request if the
> > I/O speed is down to a few k/s.
> >
> > So, could you try this patch? It won't fix anything, but if the message
> > spews all over the console, we know the 1 sector at a time retry is
> > causing the problems. If not we'll try to think of something else ...
>
> A bit unlikely, me thinks...
I can't really see any other way of getting such a massive slowdown ...
but give us your straws, we can grasp at them too ...
> Anyway, a blktrace dump of some IO would show what is going on. I'm
> assuming the problem is persistent across IO schedulers?
Yes, that might help. If it's not the one sector chunk problem it would
have to be either some strange wait issue or massive retries.
James
prev parent reply other threads:[~2008-05-28 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10810-10286@http.bugzilla.kernel.org/>
2008-05-28 17:58 ` [Bugme-new] [Bug 10810] New: Performance regression on DAC960 and kernel 2.6.24+ Andrew Morton
2008-05-28 18:34 ` James Bottomley
2008-05-28 18:37 ` Jens Axboe
2008-05-28 19:56 ` James Bottomley [this message]
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=1212004611.3445.70.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=alex@nibbles.it \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jens.axboe@oracle.com \
--cc=k-ueda@ct.jp.nec.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