From: Frans Pop <elendil@planet.nl>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: whansard@sbcglobal.net, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: disk speed regression kernel 2.6.29 and after
Date: Thu, 24 Sep 2009 20:11:18 +0200 [thread overview]
Message-ID: <200909242011.20032.elendil@planet.nl> (raw)
In-Reply-To: <200909241934.27472.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> 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.
I'm surprised at this, especially if the commit Will bisected it to [1] is
the culprit. That is a change in generic ide code and could thus very well
affect other users too.
This is a clear regression and IMHO, if it is confirmed that that commit is
the cause of the regression, it should be fixed. And if not, it could
still be worthwhile to track down which commit is the cause.
As for the lack of other reports, that could very well simply be because:
1) there are not that many users of IDE drivers anymore
2) most users don't really consciously watch their disk speed
As long as the IDE code is in mainline, I don't see why regressions should
be ignored. Adding the ide list and David to CC for other opinions.
Cheers,
FJP
[1] http://lkml.org/lkml/2009/9/23/550
next parent reply other threads:[~2009-09-24 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ABA0FDA.9090707@sbcglobal.net>
[not found] ` <200909241426.49947.bzolnier@gmail.com>
[not found] ` <20090924112645.dc97dd07.whansard@sbcglobal.net>
[not found] ` <200909241934.27472.bzolnier@gmail.com>
2009-09-24 18:11 ` Frans Pop [this message]
2009-09-24 19:12 ` disk speed regression kernel 2.6.29 and after Bartlomiej Zolnierkiewicz
2009-09-24 21:50 ` David Miller
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=200909242011.20032.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--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 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).