From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: whansard@sbcglobal.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: disk speed regression kernel 2.6.29 and after
Date: Thu, 24 Sep 2009 19:34:27 +0200 [thread overview]
Message-ID: <200909241934.27472.bzolnier@gmail.com> (raw)
In-Reply-To: <20090924112645.dc97dd07.whansard@sbcglobal.net>
On Thursday 24 September 2009 18:26:45 Will wrote:
> On Thu, 24 Sep 2009 14:26:49 +0200
> Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
> >
> >
> > I don't see how could commit 295f00 be the guilty one here. I'm suspecting
> > that bisection went wrong at some point (easy to verify by checking if commit
> > 295f00^1 is also bad).
> >
> > PS Will, it would be useful to try libata first and possibly rule out PATA out
> > of the picture completely.
>
> Disabling "ATA/ATAPI/MFM/RLL" restored my performance completely, with the
> newer kernels. I'll just have to get used my other hard drives being sdb . . ..
> Thanks guys. The copy takes right at 3m30s now.
> I made a change to dd years ago to make it default to 1 meg block size and to show
> me the "Megs copied" on screen, so I can watch how fast dd is going. With the
> older atapi drivers, this copy would be fast, but jerky and halting. With kernel
> 2.6.29 and after the halts were more frequent and longer, dragging the copy out
> to over 9 minutes in this case. With only the libata enabled, the "megs copied"
> is very smooth, with no halting, though still right at 3m30s.
> If you need me to test anything for the sake of the older drivers, I can.
> Thanks again for the help.
I'm glad to hear that the issue is fixed for you.
Regarding additional pursue of the root cause, I think that it is not worth
the effort currently since there were no other reports about similar problems
and libata is a better solution on most modern systems anyway.
next prev parent reply other threads:[~2009-09-24 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 12:08 disk speed regression kernel 2.6.29 and after will
2009-09-23 12:23 ` Jon Smirl
2009-09-24 3:06 ` Will
2009-09-24 9:10 ` Arjan van de Ven
2009-09-24 3:07 ` Robert Hancock
2009-09-24 4:35 ` Will
2009-09-24 7:44 ` odie
2009-09-24 9:01 ` Will
2009-09-24 10:41 ` Will
2009-09-24 12:26 ` Bartlomiej Zolnierkiewicz
2009-09-24 16:26 ` Will
2009-09-24 17:34 ` Bartlomiej Zolnierkiewicz [this message]
2009-09-24 18:11 ` Frans Pop
2009-09-24 19:12 ` Bartlomiej Zolnierkiewicz
2009-09-24 21:50 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2009-09-24 21:34 Andrew Randrianasulu
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=200909241934.27472.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=whansard@sbcglobal.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.